CVE-2026-49762

MEDIUMPre-NVD 5.15.1
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.1
EG Score
5.1(medium)
EG Risk
23(Track)
EG Risk 23/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity51% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated Jun 17, 2026
Patch available. Sources: github, github_commit.
github_commit

commit c64417d72fd5 (elixir-lang/elixir)

Fix landed in elixir-lang/elixir commit c64417d72fd5 — awaiting tagged release

https://github.com/elixir-lang/elixir/commit/c64417d72fd5c7d09e963ca3ac5fa2b140978d9e
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-49762
generic

Unbounded integer parsing in the Version module enables CPU and memory exhaustion denial of service | Erlang Ecosystem Foundation CNA

https://cna.erlef.org/cves/CVE-2026-49762.html
github Patch Available

Unbounded integer parsing in Version parsing/matching · Advisory · elixir-lang/elixir · GitHub

https://github.com/elixir-lang/elixir/security/advisories/GHSA-w2h8-8x3g-278p

Vendor Advisories for CVE-2026-49762(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 09:05 UTCEG score recompute
  2. 2026-07-27 09:05 UTCVendor advisory
  3. 2026-07-26 06:51 UTCEG score recompute
  4. 2026-07-26 06:51 UTCVendor advisory
  5. 2026-07-25 14:18 UTCEPSS rescore
  6. 2026-07-24 14:18 UTCEPSS rescore
  7. 2026-07-23 14:18 UTCEPSS rescore
  8. 2026-07-23 03:18 UTCEG score recompute
  9. 2026-07-22 14:08 UTCEPSS rescore
  10. 2026-07-21 15:25 UTCEPSS rescore
  11. 2026-07-20 17:08 UTCEPSS rescore
  12. 2026-07-19 14:31 UTCEPSS rescore
  13. 2026-07-19 14:31 UTCEPSS rescore
  14. 2026-07-19 02:29 UTCEPSS rescore
  15. 2026-07-18 10:04 UTCEPSS rescore
  16. 2026-07-16 17:03 UTCEPSS rescore
  17. 2026-07-15 20:12 UTCVendor advisory
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-15 02:00 UTCEPSS rescore
  21. 2026-07-14 02:22 UTCVendor advisory
  22. 2026-07-13 22:30 UTCEPSS rescore
  23. 2026-07-13 06:13 UTCEPSS rescore
  24. 2026-07-11 23:13 UTCVendor advisory
  25. 2026-07-11 08:27 UTCEPSS rescore
Show 58 more
  1. 2026-07-10 20:56 UTCVendor advisory
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-09 04:32 UTCVendor advisory
  4. 2026-07-08 15:16 UTCEPSS rescore
  5. 2026-07-08 01:52 UTCVendor advisory
  6. 2026-07-07 13:46 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-05 02:41 UTCVendor advisory
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-02 20:22 UTCVendor advisory
  12. 2026-07-01 18:01 UTCVendor advisory
  13. 2026-07-01 15:07 UTCEPSS rescore
  14. 2026-06-30 23:22 UTCEPSS rescore
  15. 2026-06-30 15:36 UTCVendor advisory
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-29 11:59 UTCVendor advisory
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 09:46 UTCVendor advisory
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-27 07:32 UTCVendor advisory
  24. 2026-06-27 03:08 UTCEPSS rescore
  25. 2026-06-26 05:18 UTCVendor advisory
  26. 2026-06-25 13:49 UTCEPSS rescore
  27. 2026-06-25 03:04 UTCVendor advisory
  28. 2026-06-24 14:05 UTCEPSS rescore
  29. 2026-06-24 00:51 UTCVendor advisory
  30. 2026-06-23 21:33 UTCEPSS rescore
  31. 2026-06-23 21:33 UTCEPSS rescore
  32. 2026-06-22 22:24 UTCVendor advisory
  33. 2026-06-22 14:25 UTCEPSS rescore
  34. 2026-06-22 14:25 UTCEPSS rescore
  35. 2026-06-21 19:31 UTCVendor advisory
  36. 2026-06-21 14:56 UTCEPSS rescore
  37. 2026-06-21 14:56 UTCEPSS rescore
  38. 2026-06-21 01:59 UTCEPSS rescore
  39. 2026-06-21 01:59 UTCEPSS rescore
  40. 2026-06-20 12:59 UTCVendor advisory
  41. 2026-06-19 19:26 UTCEPSS rescore
  42. 2026-06-19 19:26 UTCEPSS rescore
  43. 2026-06-19 10:45 UTCVendor advisory
  44. 2026-06-18 17:52 UTCEPSS rescore
  45. 2026-06-18 17:52 UTCEPSS rescore
  46. 2026-06-17 17:53 UTCEPSS rescore
  47. 2026-06-16 17:53 UTCEPSS rescore
  48. 2026-06-16 03:32 UTCVendor advisory
  49. 2026-06-15 17:49 UTCEPSS rescore
  50. 2026-06-15 17:49 UTCEPSS rescore
  51. 2026-06-14 23:18 UTCEPSS rescore
  52. 2026-06-13 23:00 UTCEPSS rescore
  53. 2026-06-12 23:12 UTCEPSS rescore
  54. 2026-06-12 23:12 UTCEPSS rescore
  55. 2026-06-11 14:00 UTCEPSS rescore
  56. 2026-06-10 22:19 UTCEPSS rescore
  57. 2026-06-09 14:12 UTCEG score recompute
  58. 2026-06-09 14:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-49762?
CVE-2026-49762 is a medium vulnerability published on June 9, 2026. 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…
When was CVE-2026-49762 disclosed?
CVE-2026-49762 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49762 actively exploited?
CVE-2026-49762 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.1% of all scored CVEs.
What is the CVSS score of CVE-2026-49762?
CVE-2026-49762 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-49762?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49762, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-49762

Explore →

Is Your Infrastructure Affected by CVE-2026-49762?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.