Description
Client-Side Enforcement of Server-Side Security vulnerability in the WebSocket connection handling of mtrudel bandit allows a remote client to keep running WebSock handler code after the server has stopped its connection, via data frames sent after ignoring the server's Close frame. When a WebSock callback returns {:stop, ...}, Bandit.WebSocket.Connection calls terminate/2, sends Close and shuts down the write side, but keeps the connection process running in a :closing state. handle_frame/3 and handle_info/3 never check that state, so later frames still reach handle_in/2 and later messages reach handle_info/2, with the state from the stop tuple, until the client sends Close, TCP drops or the idle timeout fires. A client refused in init/1 after a failed token check could still run an admin-only action. This issue affects bandit: from 0.5.1 before 1.14.0.
References6
- cna.erlef.org/cves/CVE-2026-110314.html
- github.com/mtrudel/bandit/commit/220b9dfd27f9a21305be2afc75cbe5…
- github.com/mtrudel/bandit/commit/bb407f2277dcb65a58dd8cc07913a0…
- github.com/mtrudel/bandit/security/advisories/GHSA-2v5v-8f9v-xh…
- osv.dev/vulnerability/EEF-CVE-2026-110314
- github.com/mtrudel/bandit/security/advisories/GHSA-2v5v-8f9v-xh…
Metrics
- CVSS 4.0
-
6.3
MEDIUM
Score source: CNA
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - EPSS — exploit probability
- 0% percentile: 33 · as of 8 November 2026
- CWE
- CWE-602
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.