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 is due to improper handling of HTTP/1 chunked request bodies in the function Elixir.Bandit.HTTP1.Socket:read_data/2. Specifically, the :length option that should limit the size of the accumulated request body is ignored when reading chunked transfer encoding data. Instead, all chunks are buffered into an iolist and then converted into a single binary without enforcing size limits. Because Plug.Parsers processes the request body before routing and authentication, an unauthenticated attacker can send a single chunked POST request with an arbitrarily large body to any endpoint, causing the BEAM process to exhaust system memory and be killed by the OS. The content-length request handling path correctly enforces limits and is not vulnerable. This issue affects bandit versions starting from 1.4.0 up to but not including 1.11.1. There is no vendor advisory or patch information currently available.
Potential Impact
An unauthenticated remote attacker can cause a denial of service by sending a single HTTP/1 chunked POST request with an arbitrarily large body to any path served by the vulnerable bandit versions. This leads to memory exhaustion in the BEAM process running bandit, resulting in process termination by the operating system's out-of-memory killer. This disrupts service availability and can cause downtime until the process is restarted. No authentication or valid routing is required to exploit this vulnerability.
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 at a reverse proxy or firewall to mitigate exploitation risk. Monitor for updates from the mtrudel bandit project regarding patches or official mitigations.
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2026-39803 in mtrudel bandit is due to improper handling of HTTP/1 chunked request bodies in the function Elixir.Bandit.HTTP1.Socket:read_data/2. Specifically, the :length option that should limit the size of the accumulated request body is ignored when reading chunked transfer encoding data. Instead, all chunks are buffered into an iolist and then converted into a single binary without enforcing size limits. Because Plug.Parsers processes the request body before routing and authentication, an unauthenticated attacker can send a single chunked POST request with an arbitrarily large body to any endpoint, causing the BEAM process to exhaust system memory and be killed by the OS. The content-length request handling path correctly enforces limits and is not vulnerable. This issue affects bandit versions starting from 1.4.0 up to but not including 1.11.1. There is no vendor advisory or patch information currently available.
Potential Impact
An unauthenticated remote attacker can cause a denial of service by sending a single HTTP/1 chunked POST request with an arbitrarily large body to any path served by the vulnerable bandit versions. This leads to memory exhaustion in the BEAM process running bandit, resulting in process termination by the operating system's out-of-memory killer. This disrupts service availability and can cause downtime until the process is restarted. No authentication or valid routing is required to exploit this vulnerability.
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 at a reverse proxy or firewall to mitigate exploitation risk. Monitor for updates from the mtrudel bandit project regarding patches or official mitigations.
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: 5/13/2026, 2:21:36 PM
Last enriched: 5/13/2026, 2:36:37 PM
Last updated: 5/13/2026, 4:43:52 PM
Views: 5
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.