CVE-2026-115274
Unbounded integer parsing in JSON.decode/1 enables CPU and memory exhaustion denial of service in Elixir
- Medium 6.9
Description
Improper Validation of Specified Quantity in Input vulnerability in the Elixir standard library's JSON module allows an unauthenticated attacker who supplies a JSON document to cause a denial of service through CPU and memory exhaustion. JSON.decode/1 and JSON.decode!/1 convert each integer literal with erlang:binary_to_integer/1 and do not bound its length. A literal of one million digits decodes successfully but costs 100 to 300 times as much CPU as a string of the same length, so one request body of a few megabytes holds a scheduler for about a second. A literal of more than about 1.29 million digits raises SystemLimitError. Applications generated by phx.new decode request bodies with JSON in Plug.Parsers, before routing and authentication. This issue affects elixir: from 1.18.0-rc.0 before 1.18.6, from 1.19.0-rc.0 before 1.19.7, and from 1.20.0-rc.0 before 1.20.5.
Key facts
- Published
- 30 Oct 2026
- Last changed
- 30 Oct 2026
- Assigned by
- EEF
- EPSS
- 0.498% likely to be exploited in the next 30 days, higher than 43.272% of CVEs (scores for 16 Nov 2026)
- SSVC (CISA)
- Exploitation: poc; Automatable: yes; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 6.9CVSS 4.0, Mediumfrom the CNA (EEF)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
What to do
- Decode untrusted JSON with an integer decoder that rejects long digit runs before conversion: defmodule SafeJSON do def decode!(binary) do case JSON.decode(binary, :ok, integer: &safe_integer/1) do {decoded, :ok, ""} -> decoded _ -> raise ArgumentError, "invalid JSON" end end defp safe_integer(digits) when byte_size(digits) <= 1024, do: String.to_integer(digits) defp safe_integer(_digits), do: raise(ArgumentError, "integer too long") end In Phoenix, pass SafeJSON to Plug.Parsers as json_decoder instead of Phoenix.json_library().CNA workaround statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
An unauthenticated client that sends a JSON body with integer literals of about a million digits makes the server spend about a second of CPU per request and allocate large bignums. Sustained requests exhaust CPU on applications that decode untrusted JSON with JSON, including new Phoenix applications by default. (CNA impact statement)
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| elixir-lang | elixir |
|
| elixir-lang | elixir |
|
Timeline
- 30 Oct 2026 Published
Weakness
References
- Unbounded integer parsing in JSON.decode/1 enables CPU and memory exhaustion denial of service in Elixir
- EEF CNA record for CVE-2026-115274
- OSV record EEF-CVE-2026-115274
- Introducing commit 793c114 in elixir-lang/elixir
- Fix commit c81f122 in elixir-lang/elixir
- Fix commit 7154e87 in elixir-lang/elixir
- Fix commit cd158ef in elixir-lang/elixir
- Fix commit ee5cc23 in elixir-lang/elixir