# CVE-2026-49762: Unbounded integer parsing in the Version module enables CPU and memory exhaustion denial of service

> Attackers can cause CPU and memory exhaustion denial of service by supplying large version strings to the Elixir Version module.

- **Severity:** Medium 5.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jun 2026
- **Updated:** 6 Oct 2026
- **Also known as:** AZL-89672, DEBIAN-CVE-2026-49762, EEF-CVE-2026-49762, GHSA-w2h8-8x3g-278p, OESA-2026-2787, UBUNTU-CVE-2026-49762

## What is CVE-2026-49762?

CVE-2026-49762 is a medium-severity denial of service vulnerability in elixir-lang elixir, published on 9 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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 0.9.3 before 1.20.1.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-49762?


## How do I fix CVE-2026-49762?

Upgrade to a fixed version.

## Is CVE-2026-49762 being exploited?

There is no known exploitation of CVE-2026-49762 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49762 and fix it if it is affected.

What it is: CVE-2026-49762 is a medium-severity denial of service vulnerability in elixir-lang elixir, published on 9 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49762 in the wild and no public exploit code.

Affected product: elixir-lang elixir. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49762/ (Markdown: https://insights.sbomify.com/CVE-2026-49762/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49762
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49762
- OSV: https://osv.dev/vulnerability/CVE-2026-49762

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49762/
Summaries are generated and may contain mistakes; the official description above is the record.