CVE-2026-39803: CWE-770 Allocation of Resources Without Limits or Throttling in mtrudel bandit
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
Technical Summary
The vulnerability CVE-2026-39803 in mtrudel bandit (versions 1.4.0 up to but not including 1.11.1) is due to the function 'Elixir.Bandit.HTTP1.Socket':read_data/2 ignoring the configured maximum length when reading HTTP/1 chunked request bodies. Instead of limiting the accumulated body size, the function buffers all chunks into memory unconditionally and materializes the entire body as a single binary. This behavior allows an unauthenticated remote attacker to send a chunked POST request with an arbitrarily large body, causing memory exhaustion and termination of the BEAM process by the OS out-of-memory killer. The vulnerability does not affect requests using content-length headers, which correctly enforce size limits. Because Plug.Parsers runs before routing and authentication, no valid route or credentials are needed to trigger this denial of service.
Potential Impact
An unauthenticated remote attacker can cause a denial of service by exhausting server memory through a single crafted HTTP/1 chunked POST request with an arbitrarily large body. This leads to the termination of the BEAM process by the operating system's out-of-memory killer, resulting in service disruption. There is no indication of data disclosure or code execution. The impact is limited to denial of service via resource exhaustion.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, consider implementing network-level protections such as limiting request sizes or blocking chunked transfer encoding requests from untrusted sources. Monitoring for unusually large chunked requests may help detect exploitation attempts. Avoid relying solely on application-level size limits for chunked bodies in affected versions.
CVE-2026-39803: CWE-770 Allocation of Resources Without Limits or Throttling in mtrudel bandit
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.
CVSS v4.0
Score 8.7high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2026-39803 in mtrudel bandit (versions 1.4.0 up to but not including 1.11.1) is due to the function 'Elixir.Bandit.HTTP1.Socket':read_data/2 ignoring the configured maximum length when reading HTTP/1 chunked request bodies. Instead of limiting the accumulated body size, the function buffers all chunks into memory unconditionally and materializes the entire body as a single binary. This behavior allows an unauthenticated remote attacker to send a chunked POST request with an arbitrarily large body, causing memory exhaustion and termination of the BEAM process by the OS out-of-memory killer. The vulnerability does not affect requests using content-length headers, which correctly enforce size limits. Because Plug.Parsers runs before routing and authentication, no valid route or credentials are needed to trigger this denial of service.
Potential Impact
An unauthenticated remote attacker can cause a denial of service by exhausting server memory through a single crafted HTTP/1 chunked POST request with an arbitrarily large body. This leads to the termination of the BEAM process by the operating system's out-of-memory killer, resulting in service disruption. There is no indication of data disclosure or code execution. The impact is limited to denial of service via resource exhaustion.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, consider implementing network-level protections such as limiting request sizes or blocking chunked transfer encoding requests from untrusted sources. Monitoring for unusually large chunked requests may help detect exploitation attempts. Avoid relying solely on application-level size limits for chunked bodies in affected versions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-04-07T12:28:54.916Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a0488f0cbff5d8610d62f98
Added to database: 05/13/2026, 14:21:36 UTC
Last enriched: 05/27/2026, 20:05:37 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 61
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.