CVE 8.7 HIGH

HTTP/1 chunked body reader ignores length cap in bandit_CVE-2026-39803

8.7 / 10
HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

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 'Elixir.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.

AI Analysis

Allocation of Resources Without Limits or Throttling vulnerability in bandit allowing unauthenticated remote denial of service via memory exhaustion

Basic Information

ID CVE-2026-39803
Source EEF
Published May 13, 2026 at 13:36
Modified May 13, 2026 at 14:43

Affected Product

Vendor mtrudel
Product bandit
Version 1.4.0
Affected Versions mtrudel bandit 1.4.0
mtrudel bandit 903e209a521bc216b9f9065c01ae9a0cac2d5a10

CWE Classification

AI Assessment

AI Score 8.7 / 10
AI Severity High
Vendor mtrudel
Product bandit
Version 1.4.0-1.11.0

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.