elixir-lang · Elixir · published 2026-08-28

CVE-2026-75758Unbounded recursion between Inspect.List charlist rendering and List.to_string/1 error path in Elixir

This month Public proof-of-concept exists (SSVC exploitation: poc).

CVE-2026-75758 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 8% of all CVEs. This Elixir vulnerability: CVSS 5.9 (v4.0). Fixed upstream in Elixir 1.20.4, 1.19.6, 1.18.5. Patch in your normal monthly cycle.

Share this

Remediation#

Fixed upstream in Elixir 1.20.4, 1.19.6, 1.18.5.

Patch events

  1. This monthSecurity release

    Language runtimeElixir

    Elixir security releases: 1.20.4, 1.19.6, 1.18.5

    Upgrade to 1.20.41.19.61.18.5

    Why: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (9th pct)FIRST EPSS v2026.06.15
CVSS base score5.9 (v4.0)
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CNA / CISA ADP
SSVC exploitationpocCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Uncontrolled Recursion vulnerability in the Elixir standard library allows an attacker who controls a list passed to inspect/1, List.to_string/1, or List.to_charlist/1 to exhaust a BEAM node's memory. Inspect.List's charlist branch in lib/elixir/lib/inspect.ex classifies a list as a charlist using List.ascii_printable?/2, which examines only the first :printable_limit (4096 by default) elements, and then calls IO.chardata_to_string/1 on the whole term. A list whose printable prefix exceeds that limit but which contains a later element that is not a code point (an atom, an out-of-range integer, or an improper tail) is therefore mis-classified, and the conversion raises ArgumentError. That conversion runs inside List.to_string/1, whose rescue clause builds its message by interpolating inspect(list), which re-enters the same branch and raises again. The nested inspection is an argument to raise, so the recursion is not in tail position and every level is retained: the process stack grows monotonically while each cycle re-walks the list, until the process is killed by max_heap_size or, by default, the node runs out of memory. List.to_charlist/1 has the same rescue shape. Below the printable limit the inner inspect/1 sees the invalid element within its counter and renders the list in ordinary bracket form, so a single ArgumentError is raised and no recursion occurs. This issue affects elixir: from 1.15.0-rc.0 before 1.18.5, from 1.19.0-rc.0 before 1.19.6, and from 1.20.0-rc.0 before 1.20.4.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →