CVE-2026-71562

httpc does not bound server-supplied numeric header values before integer conversion

MEDIUM
6.3
CVSS Score
Published: September 1, 2026 at 02:33 PM UTC
Updated: September 8, 2026 at 01:17 AM UTC
1 product affected across 1 vendorErlang /otp

Using OTP by Erlang?

Get instant alerts when new vulnerabilities affect OTP - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.3
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

Improper Validation of Specified Quantity in Input vulnerability in Erlang/OTP inets httpc allows a malicious or compromised HTTP server to degrade availability by returning a numeric header whose value is a very long run of digits. httpc_handler.erl converts the server-supplied Content-Length with list_to_integer/1 before comparing it against max_body_size, so the size check cannot protect the conversion, and the option defaults to nolimit in any case. The same unbounded conversion appears in httpc_response:format_response/1 for Content-Length and in httpc_response:get_ms_from_retry_after/1 for Retry-After, which is guarded only by a check that the first character is a digit. A value of up to roughly 1.26 million digits converts successfully and costs the requesting process hundreds of milliseconds of arbitrary-precision arithmetic per response. 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 17.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 inets from 5.10 before 9.3.2.7, from 9.4 before 9.6.2.3, and from 9.7 before 9.7.2. Whether OTP before OTP 17.0, corresponding to inets before 5.10, is affected is unknown.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 27.3.4.1717.0 ≤ v < 27.3.4.1728.0 ≤ v < 28.5.0.629.0 ≤ v < 29.0.65.10 ≤ v < 9.3.2.79.4 ≤ v < 9.6.2.39.7 ≤ v < 9.7.217.028.029.05.1084adefa331c4159d432d22840663c38f155cd4c19.49.7
Affected range stops below 27.3.4.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 28.5.0.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 29.0.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.6.2.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.7.2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 17.0 (unknown)
Vendor states this is fixed in 5.10 (unknown)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.3MEDIUMEEF
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-1284

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card