CVE-2026-59696

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% 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
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: None knownExposed: 0

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

Improper Validation of Specified Quantity in Input vulnerability in Erlang/OTP stdlib allows a remote attacker to degrade availability by supplying a URI whose port component is a very long run of digits.

uri_string:get_port/1 passes the port substring to binary_to_integer/1 with no length bound, catching only error:badarg, so a syntactically valid port of up to roughly 1.26 million digits converts successfully and costs the calling process hundreds of milliseconds of arbitrary-precision arithmetic. The conversion is reached from every authority-parsing path in uri_string:parse/1, including the host, registered-name, and IPv4 and IPv6 forms. parse/1 is the documented interface for parsing URIs, so any application that parses an attacker-supplied URI is exposed without further configuration. The conversion function is documented to accept integers of any size, so bounding the input is the caller's responsibility.

This issue affects OTP from OTP 21.0 before OTP 27.3.4.17, from OTP 28.0 before OTP 28.5.0.6, and from OTP 29.0 before OTP 29.0.6, corresponding to stdlib from 3.5 before 6.2.2.5, from 7.0 before 7.3.0.2, and from 8.0 before 8.0.4.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
46(Track)
EG Risk 46/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
Severity69% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 8, 2026

Advisory Details (6)

Auto-updated Sep 1, 2026
Patch available. Sources: github, github_commit.
github_commit

commit e3be1cfe9f6c (erlang/otp)

Fix landed in erlang/otp commit e3be1cfe9f6c — awaiting tagged release

https://github.com/erlang/otp/commit/e3be1cfe9f6cedd0cd20d9905e05601dfb31c8aa
github_commit

commit aba0fe8c2d70 (erlang/otp)

Fix landed in erlang/otp commit aba0fe8c2d70 — awaiting tagged release

https://github.com/erlang/otp/commit/aba0fe8c2d700bf4ac94607cf7f00e53bbe4042d
generic

Versions — Erlang System Documentation v29.0.6

https://www.erlang.org/doc/system/versions.html#order-of-versions
generic

OSV - Open Source Vulnerabilities

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

CVE-2026-59696

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

stdlib: Denial-of-Service enabled by Unbounded Integer Conversion · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-8qw4-2chm-mvj2

Vendor Advisories for CVE-2026-59696(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
erlang1:25.2.3+dfsg-1 ... 1:29.0~rc3+dfsg-4 (79 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
erlang1:27.3.4.1+dfsg-1 ... 1:29.0~rc3+dfsg-4 (40 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
erlang1:27.3.4.1+dfsg-1 ... 1:29.0~rc3+dfsg-4 (37 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 49× 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-09-19 16:25 UTCEG score recompute
  2. 2026-09-19 16:25 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 15:05 UTCEG score recompute
  5. 2026-09-18 15:05 UTCVendor advisory
  6. 2026-09-17 19:31 UTCEPSS rescore
  7. 2026-09-17 13:42 UTCEG score recompute
  8. 2026-09-17 13:42 UTCVendor advisory
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-16 12:22 UTCEG score recompute
  11. 2026-09-16 12:22 UTCVendor advisory
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 11:02 UTCEG score recompute
  14. 2026-09-15 11:02 UTCVendor advisory
  15. 2026-09-15 03:11 UTCEPSS rescore
  16. 2026-09-14 09:27 UTCEG score recompute
  17. 2026-09-14 09:27 UTCVendor advisory
  18. 2026-09-13 16:47 UTCEPSS rescore
  19. 2026-09-13 08:08 UTCEG score recompute
  20. 2026-09-13 08:08 UTCVendor advisory
  21. 2026-09-12 06:48 UTCEG score recompute
  22. 2026-09-12 06:48 UTCVendor advisory
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 05:28 UTCEG score recompute
  25. 2026-09-10 09:35 UTCEPSS rescore
Show 24 more
  1. 2026-09-09 02:47 UTCEG score recompute
  2. 2026-09-09 02:47 UTCVendor advisory
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-08 01:28 UTCEG score recompute
  5. 2026-09-08 01:28 UTCVendor advisory
  6. 2026-09-08 01:15 UTCEG score recompute
  7. 2026-09-08 01:15 UTCVendor advisory
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-07 03:59 UTCEG score recompute
  10. 2026-09-07 03:59 UTCVendor advisory
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 02:40 UTCEG score recompute
  13. 2026-09-06 02:40 UTCVendor advisory
  14. 2026-09-05 01:21 UTCEG score recompute
  15. 2026-09-05 01:21 UTCVendor advisory
  16. 2026-09-04 05:07 UTCEPSS rescore
  17. 2026-09-03 23:59 UTCVendor advisory
  18. 2026-09-02 22:40 UTCEG score recompute
  19. 2026-09-02 14:12 UTCEPSS rescore
  20. 2026-09-01 16:25 UTCEG score recompute
  21. 2026-09-01 16:10 UTCEG score recompute
  22. 2026-09-01 15:40 UTCEG score recompute
  23. 2026-09-01 14:44 UTCEG score recompute
  24. 2026-09-01 14:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59696?
CVE-2026-59696 is a medium vulnerability published on September 1, 2026. Improper Validation of Specified Quantity in Input vulnerability in Erlang/OTP stdlib allows a remote attacker to degrade availability by supplying a URI whose port component is a very long run of digits. uristring:getport/1 passes the port substring to binarytointeger/1 with no length bound,…
When was CVE-2026-59696 disclosed?
CVE-2026-59696 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59696 actively exploited?
CVE-2026-59696 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 63.9% of all scored CVEs.
What is the CVSS score of CVE-2026-59696?
CVE-2026-59696 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-59696?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59696, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59696

Explore →

Is Your Infrastructure Affected by CVE-2026-59696?

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

Start Free Scan →Browse All CVEs