Skip to content
Threat Brief

← All advisories

CVE-2026-55951

High 8.2No known exploitationFix available

httpc memory exhaustion via unbounded response header accumulation

Record last updated

CVSS score

8.2

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.7%

Higher than 54% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Weakness: CWE-770

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
* 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. Source (opens in a new tab)
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
ErlangOTP17.0Not documentedCVE Program
ErlangOTP5.10Not documentedCVE Program
ErlangOTP84adefa331c4159d432d22840663c38f155cd4c1Not documentedCVE Program
Microsoftazl3 erlang 26.2.5.21-4 on Azure Linux 3.0Not documented26.2.5.21-6Microsoft MSRC
Microsoftazl3 erlang 26.2.5.21-6 on Azure Linux 3.0Not documented26.2.5.21-6Microsoft MSRC
ErlangOTP (unaffected)aba0fe8c2d700bf4ac94607cf7f00e53bbe4042dNot documentedCVE Program
ErlangOTP (unaffected)e3be1cfe9f6cedd0cd20d9905e05601dfb31c8aaNot documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Advisory change

    Microsoft advisory revised (5.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  7. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references