CVE-2026-114213: mtrudel bandit · Unthrottled Resource Allocation
Affects mtrudel banditSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 1.14.0 soon.
Data as of 26 Oct 2026, 17:30 UTC
- Patch
- Available – fixed in 1.14.0, 220b9dfd27f9a21305be2afc75cbe585ddc24e7a
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade bandit to 1.14.0; bandit to 220b9dfd27f9a21305be2afc75cbe585ddc24e7a.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mtrudelbandit | Affected
| Fixed in
|
| banditmtrudel/bandit | Affected
| Fixed in
|
Hexbanditpkg:hex/banditOther threats | Affected
| Fixed in
|
CPE configurations (1)
cpe:2.3:a:mtrudel:bandit:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to mtrudel bandit version 1.14.0 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory. Applying the official fix fully addresses the issue.
Description
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.
References
- github.com/mtrudel/bandit/security/advisories/GHSA-cpx7-qf6w-jc63 (opens in a new tab)
- cna.erlef.org/cves/CVE-2026-114213.html (opens in a new tab)
- osv.dev/vulnerability/EEF-CVE-2026-114213 (opens in a new tab)
- github.com/mtrudel/bandit/commit/21612c7c7b1ce43eccd36d3af3a2299d23513667 (opens in a new tab)
- github.com/mtrudel/bandit/commit/220b9dfd27f9a21305be2afc75cbe585ddc24e7a (opens in a new tab)