CVE-2026-70399
High 8.7No known exploitationFix availablehttpd does not enforce the documented default max_clients connection limit
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 62% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
Allocation of Resources Without Limits or Throttling vulnerability in Erlang/OTP inets httpd allows an unauthenticated remote attacker to cause denial of service by opening and holding open a large number of connections. The max_clients option is documented to default to 150, and the inets hardening guide presents that limit as the first layer of denial-of-service defence, but a server that does not set it explicitly accepts an unlimited number of simultaneous connections. Establishing the connections is sufficient; no valid request and no authentication are required. The accept gate in httpd_manager:handle_new_connection/4 reads the option with httpd_util:lookup/2, which returns undefined when the key is absent, rather than the three-argument form carrying the 150 default that the neighbouring get_ustate/2 uses. Erlang term ordering places every integer before every atom, so the Count =< Max guard holds for any connection count and the server never returns {reject, busy}. Each accepted connection occupies a worker process and a socket for as long as it is held, driving the node towards process, memory and file descriptor exhaustion. Servers that set max_clients explicitly are unaffected, because a configured value is applied as intended. This issue affects OTP from OTP 17.0 before OTP 27.3.4.17, OTP 28.5.0.6, and OTP 29.0.6, corresponding to inets from 5.10 before 9.3.2.7, 9.6.2.3, and 9.7.2.
Weakness: CWE-770
Patching and mitigation
- Patch status
- Fix available (source: CVE record (EEF))
- Fix documented (source date)
- Mitigation
- * Set max_clients explicitly in the httpd configuration, for example {max_clients, 150}. An explicitly configured value is read by the same accept gate and applied as intended, so this restores the documented limit without upgrading. * Limit concurrent connections in front of httpd, for example with reverse proxy or firewall connection-count and connection-rate rules. * Restrict access to the server to trusted clients where the deployment allows it. Source (opens in a new tab)
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Erlang | OTP | 17.0 | Not documented | CVE Program |
| Erlang | OTP | 5.10 | Not documented | CVE Program |
| Erlang | OTP | d9674f32811cd5bb02b0d6656053b5ee226bc74c | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (EEF)
Vendor guidance and references
- Fix commit 6746dc4 in erlang/otp (opens in a new tab)patch
- Fix commit d94a94c in erlang/otp (opens in a new tab)patch
- Fix commit e0050fc in erlang/otp (opens in a new tab)patch
- https://github.com/erlang/otp/security/advisories/GHSA-pwvh-c689-f8q5 (opens in a new tab)related, vendor-advisory
- EEF CNA record for CVE-2026-70399 (opens in a new tab)related
- Introducing commit d9674f3 in erlang/otp (opens in a new tab)related
- OSV record EEF-CVE-2026-70399 (opens in a new tab)related
- Erlang/OTP version ordering (opens in a new tab)x_version-scheme