CVE-2026-49762: Unbounded integer parsing in the Version module enables CPU and memory exhaustion denial of service
Noroxi assessment
Priority: Monitor (action score 20/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: elixir-lang elixir 1.20.1, 64e6707233464c3e55a9ca6b44019aed25b0390a, c64417d72fd5c7d09e963ca3ac5fa2b140978d9e; azl3 elixir 1.16.1-1 on Azure Linux 3.0 1.16.1-2; azl3 elixir 1.16.1-2 on Azure Linux 3.0 1.16.1-2.
Low priority for now. Upgrade to elixir-lang elixir 1.20.1, 64e6707233464c3e55a9ca6b44019aed25b0390a, c64417d72fd5c7d09e963ca3ac5fa2b140978d9e; azl3 elixir 1.16.1-1 on Azure Linux 3.0 1.16.1-2; azl3 elixir 1.16.1-2 on Azure Linux 3.0 1.16.1-2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 0.9.3 before 1.20.1.
- Published
- Jun 9, 2026
- Updated
- Oct 6, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-400
Report tools
Action score
20
Monitor
Low priority for now.
- CVSS
- 20 / 40 · 5.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · EEF
- 5.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (EEF). Independent of NVD's CPE analysis and usually ahead of it.
elixir-lang elixir
- 0.9.3 and later · before 1.20.1affected · semver
- 057691722eb8cfe315f5606358954a2b173ff7a3 and lateraffected · gitfixed in c64417d72fd5c7d09e963ca3ac5fa2b140978d9e, 64e6707233464c3e55a9ca6b44019aed25b0390a
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | elixir-lang | from 0 | — |
| Debian:14 | elixir-lang | before 1.20.1.dfsg-1 | 1.20.1.dfsg-1 |
Same product
elixir-lang: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-115274Unbounded integer parsing in JSON.decode/1 enables CPU and memory exhaustion denial of service in Elixir27Monitor
- CVE-2026-109821Unbounded port parsing in URI.parse/1 enables CPU exhaustion denial of service in Elixir25Monitor
- CVE-2026-75758Unbounded recursion between Inspect.List charlist rendering and List.to_string/1 error path in Elixir23Monitor
Published before and after this one in the same product
- Later →CVE-2026-97209Oct 30, 2026 · Insecure temporary file in mix deps.partition lets a local user execute code in another user's dependency build21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| elixir-lang elixir | 1.20.1 | Vendor (CNA) |
| elixir-lang elixir | 64e6707233464c3e55a9ca6b44019aed25b0390a | Vendor (CNA) |
| elixir-lang elixir | c64417d72fd5c7d09e963ca3ac5fa2b140978d9e | Vendor (CNA) |
| azl3 elixir 1.16.1-1 on Azure Linux 3.0 | 1.16.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 elixir 1.16.1-2 on Azure Linux 3.0 | 1.16.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:elixir-lang | 1.20.1.dfsg-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Peter Ullrichfinder
- José Valimremediation developer
- Eric Meadows-Jönssonremediation reviewer
- Jonatan Männchen / EEFanalyst
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-109821143 days apartUnbounded port parsing in URI.parse/1 enables CPU exhaustion denial of service in Elixir25Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- github.com/elixir-lang/elixir/commit/057691722eb8cfe315f5606358954a2b173ff7a3
- github.com/elixir-lang/elixir/commit/64e6707233464c3e55a9ca6b44019aed25b0390a
- github.com/elixir-lang/elixir/commit/c64417d72fd5c7d09e963ca3ac5fa2b140978d9e
- github.com/elixir-lang/elixir/security/advisories/GHSA-w2h8-8x3g-278p
- osv.dev/vulnerability/EEF-CVE-2026-49762
Vendor advisories and official records. Exploit/PoC links are deliberately left out.