CVE-2026-59696

uri_string does not bound the port component of a URI before integer conversion

State
Published
Severity
6.9 Medium
Published
Sep 1, 2026
Updated
Sep 8, 2026
Reserved
Jul 6, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
4.06.9 MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NEEF

Weaknesses

  • CWE-1284 Improper Validation of Specified Quantity in Input

Affected Products

ProductVersions
OTPErlang
  • 21.0 to before 27.3.4.17Affected
  • 28.0 to before 28.5.0.6Affected
  • 29.0 to before 29.0.6Affected
OTPErlang
  • 3.5 to before 6.2.2.5Affected
  • 7.0 to before 7.3.0.2Affected
  • 8.0 to before 8.0.4Affected
OTPErlang
  • 29a9dd0e17a97a3e6e46f0d08c6ba8f31db33f5e and laterAffectedfrom aba0fe8c2d700bf4ac94607cf7f00e53bbe4042dNot affectedfrom e3be1cfe9f6cedd0cd20d9905e05601dfb31c8aaNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.