httpd applies no timeout while receiving a request body, parking a worker on a stalled client
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-71380
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 19:03 UTC · Revision 1
Source evidence
httpd applies no timeout while receiving a request body, parking a worker on a stalled client
core-osv · Original sourcePublished 1 Sept 2026, 14:35 UTC
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.
osv:CVE-2026-71380
Complete source record
{
"id": "33b237914ae117651b640bde11f399a6837d0b973c8e160517cde4c5a976a4c3",
"url": "https://osv.dev/vulnerability/CVE-2026-71380",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "httpd applies no timeout while receiving a request body, parking a worker on a stalled client",
"summary": "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.",
"evidence": "osv:CVE-2026-71380",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-71380",
"aliases": [
"CVE-2026-71380",
"EEF-CVE-2026-71380",
"GHSA-5vp4-58hc-h8cc"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/erlang/otp",
"type": "GIT",
"events": [
{
"introduced": "84adefa331c4159d432d22840663c38f155cd4c1"
},
{
"fixed": "81b453aac5a006bb8d26405f2bc3cf24e9d7733c"
},
{
"introduced": "07b8f441ca711f9812fad9e9115bab3c3aa92f79"
},
{
"fixed": "79157f447019730504f6f6c43c9b1d1cfa1d4192"
},
{
"introduced": "9e6f6742c4d9e9915ee8af0dcb7d97cf1f836116"
},
{
"fixed": "e7252384d42f124c07bec5c79eebd7ea9cdd5100"
},
{
"introduced": "550d7b7898706c7822362c42e7b93120c1d1f29a"
},
{
"fixed": "e07fd07837e5aa845657f5fa340637121e451d47"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "84adefa331c4159d432d22840663c38f155cd4c1"
},
{
"fixed": "81b453aac5a006bb8d26405f2bc3cf24e9d7733c"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"introduced": "17.0"
},
{
"fixed": "27.3.4.17"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"introduced": "28.0"
},
{
"fixed": "28.5.0.6"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"introduced": "29.0"
},
{
"fixed": "29.0.6"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"fixed": "81b453aac5a006bb8d26405f2bc3cf24e9d7733c"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"patch-base-27",
"OTP-27.3.4",
"patch-base-28",
"OTP-28.5",
"OTP-29.0",
"OTP-29.0.5",
"OTP-27.3.4.9",
"OTP-27.3.4.10",
"OTP-29.0.2",
"OTP-28.5.0.2",
"OTP-28.5.0.5",
"OTP-27.3.4.14",
"OTP-27.3.4.16",
"OTP-29.0.3",
"OTP-27.3.4.15",
"OTP-28.5.0.4",
"OTP-29.0.4",
"OTP-28.5.0.3",
"OTP-27.3.4.13",
"OTP-28.4",
"OTP-27.3.4.12",
"OTP-28.5.0.1",
"OTP-29.0.1",
"OTP-27.0",
"OTP-27.3.4.11",
"OTP-28.0",
"OTP-27.3.4.8",
"OTP-27.3.4.6",
"OTP-27.3.4.7",
"OTP-27.3",
"OTP-27.3.4.5",
"OTP-27.3.4.4",
"OTP-28.1",
"OTP-27.3.4.3",
"OTP-27.3.3",
"OTP-27.3.4.2",
"OTP-26.0",
"OTP-25.0",
"OTP-27.3.4.1",
"OTP-27.3.2",
"OTP-27.2",
"OTP-27.3.1",
"OTP-27.1",
"OTP-27.0-rc3",
"OTP-27.0-rc2",
"OTP-27.0-rc1",
"OTP-24.0",
"OTP-26.0-rc3",
"OTP-26.0-rc2",
"OTP-26.0-rc1",
"OTP-23.0",
"OTP-21.0",
"OTP-25.0-rc3",
"OTP-25.0-rc2",
"OTP-25.0-rc1",
"OTP-22.0",
"OTP-24.0-rc3",
"OTP-24.0-rc2",
"OTP-24.0-rc1",
"OTP-23.0-rc3",
"OTP-23.0-rc2",
"OTP-23.0-rc1",
"OTP-20.0",
"OTP-22.0-rc3",
"OTP-22.0-rc2",
"OTP-22.0-rc1",
"OTP-19.0",
"OTP-21.0-rc2",
"OTP-18.0",
"OTP-21.0-rc1",
"OTP-17.0",
"OTP-20.0-rc2",
"OTP-20.0-rc1",
"OTP-19.0-rc2",
"OTP-19.0-rc1",
"OTP-18.0-rc1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-71380.json"
}
}
],
"modified": "2026-10-28T02:30:31.697144764Z",
"provider": "osv",
"references": [
"https://cna.erlef.org/cves/CVE-2026-71380.html",
"https://github.com",
"https://osv.dev/vulnerability/EEF-CVE-2026-71380",
"https://www.erlang.org/doc/system/versions.html#order-of-versions",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/71xxx/CVE-2026-71380.json",
"https://github.com/erlang/otp/security/advisories/GHSA-5vp4-58hc-h8cc",
"https://nvd.nist.gov/vuln/detail/CVE-2026-71380",
"https://github.com/erlang/otp/commit/81b453aac5a006bb8d26405f2bc3cf24e9d7733c",
"https://github.com/erlang/otp"
],
"provider_metadata": {
"cwe_ids": [
"CWE-772"
],
"cna_assigner": "EEF",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"introduced": "5.10"
},
{
"fixed": "9.3.2.7"
},
{
"introduced": "9.4"
},
{
"fixed": "9.6.2.3"
},
{
"introduced": "9.7"
},
{
"fixed": "9.7.2"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/71xxx/CVE-2026-71380.json"
}
},
"related_cves": [
{
"value": "CVE-2026-71380",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 498601,
"published_at": "2026-09-01T14:35:31.192+00:00"
}