Quick answers
- Is CVE-2026-110314 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110314 being exploited in the wild.
- How severe is CVE-2026-110314?
- Informational severity, published 26 October 2026.
- Which products and versions are affected?
- Mtrudel Bandit 0.5.1 to before 1.14.0.
- Is there a fix for CVE-2026-110314?
- 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-110314 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-110314?
- 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 exists in Bandit's WebSocket.Connection module when a callback returns {:stop, ...}. The connection process enters a :closing state after sending a Close frame and shutting down the write side, but the handle_frame/3 and handle_info/3 functions do not check this state, allowing further frames to reach handle_in/2 and messages to reach handle_info/2. A client rejected during init/1 due to failed authentication can exploit this to execute admin-only actions before the connection fully terminates.
Affected products
- mtrudel Bandit 0.5.1 to before 1.14.0
Timeline
- 2026-10-26: disclosed