Skip to content
Threat Brief

← All advisories

CVE-2026-39803

High 8.7No known exploitationFix available

HTTP/1 chunked body reader ignores length cap in bandit

Record last updated

CVSS score

8.7

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.6%

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

CISA remediation deadline

None

Not in the KEV catalog

Description

Allocation of Resources Without Limits or Throttling vulnerability in mtrudel bandit allows unauthenticated remote denial of service via memory exhaustion. The chunked clause of Bandit.HTTP1.Socket.read_data/2 in lib/bandit/http1/socket.ex ignores the caller-supplied :length option when reading HTTP/1 chunked request bodies. Instead of capping the accumulated body at the configured limit (e.g. Plug.Parsers' default 8 MB), do_read_chunked_data!/5 buffers every received chunk into an iolist unconditionally and materializes the entire body as a single binary. The function always returns {:ok, body, ...}, so callers cannot interpose a 413 response. Because Plug.Parsers runs before routing and authentication in the standard Phoenix endpoint, an unauthenticated attacker needs no valid route or credentials. Sending a single Transfer-Encoding: chunked POST request with an arbitrarily large body to any path causes the BEAM process to exhaust available memory and be terminated by the OS OOM killer. The content-length path in the same function correctly enforces the limit and is not affected. This issue affects bandit: from 1.4.0 before 1.11.1.

Weakness: CWE-770

Patching and mitigation

Patch status
Fix available (source: NVD (reference tagged Patch))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
mtrudelbanditfrom 1.4.0 before 1.11.11.11.1NIST NVD
mtrudelbanditfrom 1.4.0 before 1.11.11.11.1CVE Program
mtrudelbanditfrom 903e209a521bc216b9f9065c01ae9a0cac2d5a10 before ae3520dfdbfab115c638f8c7f6f6b805db34e1abae3520dfdbfab115c638f8c7f6f6b805db34e1abCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by NVD (reference tagged Patch)

    Source: NVD (reference tagged Patch) (opens in a new tab)

Vendor guidance and references