Chunk extensions accept bare LF and CR, enabling request smuggling in Bandit
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- —
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA.
Summary
Bandit, an Elixir HTTP server, contains an HTTP request smuggling flaw in its HTTP/1.1 chunked body reader in versions from 1.12.4 before 1.14.0. The reader ends the chunk-size line at the first CRLF and does not validate chunk extensions, so a bare LF is accepted and can be read differently by a front-end proxy (CWE-444). An unauthenticated remote attacker can smuggle a second request past such a proxy. Deployments without a proxy in front of Bandit are not affected.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
Description from the CNA
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') vulnerability in the HTTP/1.1 chunked body reader of mtrudel bandit allows an unauthenticated remote attacker to smuggle a second request past a front-end proxy via a chunk extension that contains a bare LF. The chunked reader in lib/bandit/http1/socket.ex takes the chunk-size line to be everything up to the first CRLF and discards everything after ; without checking it against the RFC 9112 chunk-ext grammar, so bare LF, bare CR and other control bytes pass. A proxy that ends the size line at a bare LF reads 2;\nxx\r\n40\r\n... as one request whose second chunk holds a GET /admin, while Bandit ends the body early and dispatches GET /admin as a separate pipelined request. Deployments without such a proxy in front of Bandit are not affected. This issue affects bandit: from 1.12.4 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, which fixes the issue. The sources list no other fixed versions or vendor advisories for Bandit.
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-80371 WebSocket 1-byte continuation frames exhaust memory in BanditPriority MEDIUM 45
Timeline
- 2026-10-26 Threatist record created from CVE-2026-114216
- 2026-10-26 CISA SSVC decision points changed
- 2026-10-26 Priority changed: MEDIUM → LOW
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