# CVE-2026-110314: Bandit WebSocket connection state-checking bypass

Source: https://junglewise.ai/threats/cve-2026-110314-client-side-enforcement-of-server-side-security-vulnerability-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-26. Updated: 2026-10-26  
License: CC BY 4.0 with a link back

CVE-2026-110314 · Severity: info · Published 2026-10-26

Bandit is an Elixir web server library that handles WebSocket connections. After a server closes a WebSocket connection, a remote client can continue sending data frames and trigger code execution using the stale connection state, potentially bypassing authentication checks that should have rejected the connection. This allows attackers to run privileged operations after being denied access.

Technologies: [Mtrudel Bandit](https://junglewise.ai/threats/technologies/mtrudel-bandit). Vendors: [Mtrudel](https://junglewise.ai/threats/vendors/mtrudel).

## 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

## References

- [https://repo.hex.pm/](https://repo.hex.pm/)
- [https://github.com/](https://github.com/)

## Related threats

- [mtrudel bandit resource exhaustion in HTTP/2 request body reader](https://junglewise.ai/threats/cve-2026-116078-allocation-of-resources-without-limits-or-throttling)
- [mtrudel bandit HTTP/2 stream resource exhaustion](https://junglewise.ai/threats/cve-2026-115269-allocation-of-resources-without-limits-or-throttling)
- [mtrudel bandit WebSocket denial of service via fragmented messages](https://junglewise.ai/threats/cve-2026-114213-allocation-of-resources-without-limits-or-throttling)
- [mtrudel bandit inefficient algorithmic complexity in header parser](https://junglewise.ai/threats/cve-2026-113436-inefficient-algorithmic-complexity-vulnerability-in-the-header)
- [mtrudel bandit HTTP/2 handler resource limit bypass](https://junglewise.ai/threats/cve-2026-111103-improper-cleanup-on-thrown-exception-vulnerability-in-the-http-2)