CVE-2026-71380

httpd applies no timeout while receiving a request body, parking a worker on a stalled client

HIGH
8.7
CVSS Score
Published: September 1, 2026 at 02:35 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
HIGH8.7
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

Missing Release of Resource after Effective Lifetime vulnerability in Erlang/OTP inets httpd allows an unauthenticated remote attacker to cause denial of service by sending valid request headers with a large Content-Length and then stalling before the body is complete. httpd_request_handler:handle_info/2 cancels the request timeout as soon as a parse step succeeds, which includes the headers, and the clause that handles a decoder asking for more data re-arms the socket with {active, once} without setting any further timer. httpd_request:whole_body/2 returns such a continuation whenever the bytes received are fewer than the announced Content-Length, so a well-formed request that stops mid-body leaves the worker waiting indefinitely. The periodic byte-rate check that would reclaim it is armed only when minimum_bytes_per_second is configured, which it is not by default. Repeating this across connections occupies every worker permitted by max_clients and denies service to legitimate clients at negligible bandwidth cost. 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
Vendor states this is fixed in 81b453aac5a006bb8d26405f2bc3cf24e9d7733c (fixed)
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)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

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

CVSS

8.7HIGHEEF
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-772

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