Technical impact
Elixir's core JSON module can parse integer literals of arbitrary length without bounding the size of the digit string. Converting a very long integer consumes 100‑300 times more CPU cycles than parsing a string of equal length, and a literal exceeding approximately 1.29 million digits triggers a SystemLimitError. An unauthenticated attacker can send such a payload in an HTTP request, exhausting a scheduler process for up to a second and potentially disrupting service availability. The weakness is an instance of unbounded resource allocation (CWE-770) and improper quantity validation (CWE-1284).
Affected Systems
The flaw exists in Elixir releases from 1.18.0‑rc.0 up through 1.18.5, from 1.19.0‑rc.0 through 1.19.6, and from 1.20.0‑rc.0 through 1.20.4. Any application that uses Elixir's JSON.decode/1 or JSON.decode!/, especially web frameworks that automatically parse request bodies (e.g., Phoenix), is vulnerable.
Risk and Exploitability
With a CVSS score of 6.9 the vulnerability is of moderate severity, and the EPSS score of < 1% indicates a very low exploitation probability. The vulnerability is not listed in the CISA KEV catalog. The attack vector is likely a simple unauthenticated HTTP POST containing an oversized integer value in the JSON body—a scenario that does not require prior authentication or privileged access. Given that the issue resides in the language core, deploying the fix promptly is essential to reduce the window of exposure.