CVE-2026-49762

Unbounded integer parsing in the Version module enables CPU and memory exhaustion denial of service

MEDIUM
5.1
CVSS Score
Published: June 9, 2026 at 02:04 PM UTC
Updated: October 6, 2026 at 09:17 AM 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.1
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

Uncontrolled Resource Consumption vulnerability in the Elixir standard library's Version module allows an attacker who controls a version string to cause a denial of service through CPU and memory exhaustion. The version parser converts numeric version components (major, minor, patch and numeric pre-release/build identifiers) to integers without bounding their length. A single large all-digit component therefore forces a super-linear, non-yielding base-10 to arbitrary-precision integer conversion (String.to_integer/1, i.e. :erlang.binary_to_integer/1) that pins a BEAM scheduler, and a larger component raises an uncaught SystemLimitError that crashes the calling process. A single moderately sized string (around one megabyte) is enough; no authentication is required. This is reachable from the public entry points Version.parse/1, Version.parse!/1, Version.match?/3, Version.compare/2, and Version.parse_requirement/1, which applications routinely call on untrusted input such as HTTP parameters, dependency-manifest fields, and package metadata. This vulnerability is associated with program files lib/version.ex and program routines 'Elixir.Version.Parser':parse_digits/2. This issue affects Elixir: from 1.5.0 before 1.20.1.

Affected

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

1.5.0 ≤ v < 1.20.11.5.063e186aea94395897dc4964d82d250130c01ec25
Vendor states this is fixed in c64417d72fd5c7d09e963ca3ac5fa2b140978d9e (fixed)
Affected range stops below 1.20.1, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

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

CVSS

5.1MEDIUMEEF
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-400

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