PoC Monitor
← All CVEs
CVE-2026-70399published 1 Sep 2026 14:33 UTCData: JSON · API

Erlang OTP

httpd does not enforce the documented default max_clients connection limit

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.7high · scored by CNA · CWE-770
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Erlang OTP
  • >= 5.10, < *

Fixed in *, 9.3.2.7, 9.6.2.3, 9.7.2

Erlang OTP
  • >= 17.0, < *

Fixed in *, 27.3.4.17, 28.5.0.6, 29.0.6

Erlang OTP
  • >= d9674f32811cd5bb02b0d6656053b5ee226bc74c, < *

Fixed in *, 6746dc4e1df5257ad8ac91cbbd167cb8b0274ce7, d94a94c96eb4cccbd6f7d7da5975f0c035b69612, e0050fc00c500a4fa9ba1f594603c787ff6d20b2

Mitigation

Upgrade OTP to * or 9.3.2.7 or 9.6.2.3 or 9.7.2 or later.

Upgrade OTP to * or 27.3.4.17 or 28.5.0.6 or 29.0.6 or later.

Upgrade OTP to * or 6746dc4e1df5257ad8ac91cbbd167cb8b0274ce7 or d94a94c96eb4cccbd6f7d7da5975f0c035b69612 or e0050fc00c500a4fa9ba1f594603c787ff6d20b2 or later.

Workaround

* 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.

References

2 more

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published1 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.