CVE-2026-49762
Last modified
CVE-2026-49762 is a medium-severity vulnerability rated 5.1/10 on the CVSS scale. 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. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-49762?
How severe is CVE-2026-49762?
How do I fix CVE-2026-49762?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-49755Improper Handling of Highly Compressed Data (Data Amplificat…7.5
- CVE-2026-49756Improper Neutralization of CRLF Sequences ('CRLF Injection')…3.7
- CVE-2026-49757Authentication Bypass by Spoofing vulnerability in team-alem…9.2
- CVE-2026-49759Stack-based Buffer Overflow vulnerability in Erlang OTP erts…8.2
- CVE-2026-4976A vulnerability was found in Totolink LR350 9.3.5u.6369_B202…8.8
- CVE-2026-49760Stack-based Buffer Overflow vulnerability in Erlang OTP (erl…5.5
- CVE-2026-49763Unauthenticated PHP Object Injection in Integration for Cont…9.8
- CVE-2026-49764Unauthenticated Broken Authentication in RegistrationMagic <…9.8
- CVE-2026-49765Unauthenticated PHP Object Injection in Integration for Mail…9.8
- CVE-2026-49766Subscriber Arbitrary File Deletion in WP User Manager <= 2.9…9.9
- CVE-2026-49767Unauthenticated Broken Authentication in wpForo Forum <= 3.1…9.8
- CVE-2026-49768Unauthenticated PHP Object Injection in Happyforms <= 1.26.1…9.8
Are you affected by CVE-2026-49762?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
