Erlang · Erlang/OTP · published 2026-09-01
CVE-2026-59696uri_string does not bound the port component of a URI before integer conversion
Routine No exploitation evidence; EPSS 0.6%.
CVE-2026-59696 is not known to be exploited in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 48% of all CVEs. This Erlang/OTP vulnerability: CVSS 6.9 (v4.0), attacks can be automated. Fixed upstream in Erlang/OTP 29.1.2, 29.0.6, 28.5.0.8, 28.5.0.6 (+2 more). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Erlang/OTP 29.1.2, 29.0.6, 28.5.0.8, 28.5.0.6, 27.3.4.19, 27.3.4.17.
Patch events
Language runtimeErlang/OTP
Erlang/OTP security fixes: 16 CVEs
Upgrade to
29.1.229.0.628.5.0.828.5.0.627.3.4.1927.3.4.17Why: CVE-2026-69664: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.6% (49th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 6.9 (v4.0)CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Erlang OTP
21.0to before*(affected)
- Erlang OTP
3.5to before*(affected)
- Erlang OTP
29a9dd0e17a97a3e6e46f0d08c6ba8f31db33f5eto before*(affected)
Description (from the CVE record)#
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, OTP 28.5.0.6, and OTP 29.0.6, corresponding to stdlib from 3.5 before 6.2.2.5, 7.3.0.2, and 8.0.4.
Quoted from the CVE Program record.