WebSocket 1-byte continuation frames exhaust memory in Bandit
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-770.
Summary
Bandit, an Elixir HTTP server, from 1.11.0 before 1.14.0 is affected. The WebSocket fragment reassembly does not limit the number of fragments, so it counts only payload bytes against max_fragmented_message_size. An unauthenticated remote attacker can send a fragmented message made of many 1-byte continuation frames, using CWE-770 (allocation of resources without limits), to exhaust server memory. Ping frames between fragments keep the connection open past the idle timeout.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
Description from the CNA
Allocation of Resources Without Limits or Throttling vulnerability in the WebSocket fragment reassembly of mtrudel bandit allows an unauthenticated remote attacker to exhaust server memory via a fragmented message made of many 1-byte continuation frames. Bandit.WebSocket.Connection checks max_fragmented_message_size against the payload bytes received, but keeps every non-final continuation frame as a new list cell around its own binary, and nothing limits the number of fragments. A 1-byte fragment costs 7 bytes on the wire but about 150 to 170 bytes of server memory, so one connection can hold about 150 times the configured limit, roughly 1.2 to 1.4 GB at the default 8 MB. Ping frames between fragments keep the connection alive past the idle timeout. This issue affects bandit: from 1.11.0 before 1.14.0.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade bandit to version 1.14.0 or later, which fixes the issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
- Fix · CNA bandit (mtrudel) Fixed in 1.14.0
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
mtrudel bandit 1.14.0, 220b9dfd27f9a21305be2afc75cbe585ddc24e7a
11 records Highest priority Priority MEDIUM 10 MEDIUM, 1 LOW
Other records, highest priority first
- TI-2026-80361 Bandit frames still reach WebSock after server-initiated closePriority MEDIUM 61
- TI-2026-80382 HTTP/2 frames let clients hold Bandit request body reads openPriority MEDIUM 45
- TI-2026-80369 Quadratic bignum parsing of Content-Length and Host port values in BanditPriority MEDIUM 45
Timeline
- 2026-10-26 Threatist record created from CVE-2026-114213
- 2026-10-26 CISA SSVC decision points changed
References
More mtrudel vulnerabilities
- TI-2026-81989 HTTP/2 request bodies made of 1-byte DATA frames amplify memory use in Bandit CVSS 4.0HIGH 8.7
- TI-2026-74311 Bandit HTTP/2 send timers reset, letting trickles pin stream processes CVSS 4.0HIGH 8.7
- TI-2026-52571 HTTP/2 connection-window starvation pins Plug processes indefinitely in Bandit CVSS 4.0HIGH 8.7
- TI-2026-46780 Quadratic CPU blow-up reassembling fragmented WebSocket messages in Bandit CVSS 4.0HIGH 8.7
- TI-2026-31007 WebSocket fragmented message reassembly unbounded in bandit CVSS 4.0HIGH 8.7
- TI-2026-28689 HTTP/1 chunked decoder infinite loop on requests with trailer fields in bandit CVSS 4.0HIGH 8.7
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences