CVE-2026-75758

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

MEDIUM
5.9
CVSS Score
Published: August 28, 2026 at 11:28 AM UTC
Updated: September 1, 2026 at 09:31 PM UTC
1 product affected across 1 vendorElixir

Using elixir by elixir-lang?

Get instant alerts when new vulnerabilities affect elixir - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.9
Exploit prediction
EPSS 0.2%
SSVC
PoC

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.15.0-rc.0 ≤ v < 1.18.51.19.0-rc.0 ≤ v < 1.19.61.20.0-rc.0 ≤ v < 1.20.41.15.0-rc.01.19.0-rc.01.20.0-rc.09718f2b90ce086ff8614d5782f4ec528495c98dd
Affected range stops below 1.18.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.19.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.20.4, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.9MEDIUMEEF
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-674

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card