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

Erlang OTP

httpc memory exhaustion via unbounded response header accumulation

The Erlang/OTP httpc HTTP client does not enforce a limit on the total size of response headers received from a server. The max_header_size option defaults to nolimit, and httpc_response:parse_headers/6 accumulates every header into a list before the length check runs (which only fires after the terminating CRLF CRLF is received). A malicious or compromised HTTP server can send an arbitrarily large number of headers, or headers with very large values, causing the client process to allocate unbounded memory until the system runs out of memory or the BEAM VM crashes. A proof-of-concept server sending 100,000 headers of roughly 4000 bytes each caused the client VM to allocate over 13 GB of memory in under 30 seconds. Any application using httpc:request/4,5 to connect to untrusted servers is affected. No authentication is required: any server the client connects to (including via a redirect or man-in-the-middle) can trigger the exhaustion. 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. Whether OTP before OTP 17.0, corresponding to inets before 5.10, is affected is unknown.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.2high · 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
  • >= 84adefa331c4159d432d22840663c38f155cd4c1, < *

Fixed in *, aba0fe8c2d700bf4ac94607cf7f00e53bbe4042d, e3be1cfe9f6cedd0cd20d9905e05601dfb31c8aa

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 aba0fe8c2d700bf4ac94607cf7f00e53bbe4042d or e3be1cfe9f6cedd0cd20d9905e05601dfb31c8aa or later.

Workaround

* Restrict httpc to trusted servers only, and avoid using it to fetch resources from arbitrary or user-supplied URLs. * Apply operating-system memory limits (cgroups,ulimit) to contain the blast radius of a runaway client process. * Use an alternative HTTP client library that enforces a response header size limit.

References

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.