Answer in brief
CVE-2026-59696 records a Unknown severity vulnerability in uri_string does not bound the port component of a URI before integer conversion. The current sources do not mark it as known exploited. The current feed maps Erlang/OTP (generic), Erlang/OTP (generic), Erlang/OTP (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Erlang/OTP (generic), Erlang/OTP (generic), Erlang/OTP (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Erlang/OTPgeneric | >=21.0 <27.3.4.17 || >=28.0 <28.5.0.6 || >=29.0 <29.0.6 | 27.3.4.17, 28.5.0.6, 29.0.6 |
| Erlang/OTPgeneric | >=3.5 <6.2.2.5 || >=7.0 <7.3.0.2 || >=8.0 <8.0.4 | 6.2.2.5, 7.3.0.2, 8.0.4 |
| Erlang/OTPgeneric | >=29a9dd0e17a97a3e6e46f0d08c6ba8f31db33f5e <* | * |
Published upstream
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 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. 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.
Quoted source text, attributed separately from HOL analysis.