Answer in brief
CVE-2026-71380 records a Unknown severity vulnerability in httpd applies no timeout while receiving a request body, parking a worker on a stalled client. 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 | >=17.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 | >=5.10 <9.3.2.7 || >=9.4 <9.6.2.3 || >=9.7 <9.7.2 | 9.3.2.7, 9.6.2.3, 9.7.2 |
| Erlang/OTPgeneric | >=84adefa331c4159d432d22840663c38f155cd4c1 <81b453aac5a006bb8d26405f2bc3cf24e9d7733c | 81b453aac5a006bb8d26405f2bc3cf24e9d7733c |
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
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.
Quoted source text, attributed separately from HOL analysis.