Quick answers
- Is CVE-2026-114213 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114213 being exploited in the wild.
- How severe is CVE-2026-114213?
- Informational severity, published 26 October 2026.
- Which products and versions are affected?
- Mtrudel Bandit 1.11.0 before 1.14.0.
- Is there a fix for CVE-2026-114213?
- Yes: fixed in 1.14.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114213 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-114213?
- Check whether you run Mtrudel Bandit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.14.0
Technical details
The vulnerability is an unbounded resource allocation in WebSocket fragment reassembly: Bandit.WebSocket.Connection checks max_fragmented_message_size against payload bytes but stores each non-final continuation frame as a separate list cell, with no limit on fragment count. A 1-byte fragment consumes 150–170 bytes of server memory, allowing an attacker to exceed the configured limit by 150×. Ping frames can reset the idle timeout, keeping the connection alive and memory allocated.
Affected products
- mtrudel bandit 1.11.0 before 1.14.0
Timeline
- 2026-10-26: disclosed