Answer in brief
CVE-2026-110314 records a Medium severity (CVSS 6.3) vulnerability in WebSocket frames keep reaching the WebSock after a server-initiated close in Bandit. The current sources do not mark it as known exploited. The current feed maps mtrudel/bandit (generic), mtrudel/mtrudel/bandit (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps mtrudel/bandit (generic), mtrudel/mtrudel/bandit (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| mtrudel/banditgeneric | >=0.5.1 <1.14.0 | 1.14.0 |
| mtrudel/mtrudel/banditgeneric | >=bb407f2277dcb65a58dd8cc07913a0b58a80e266 <220b9dfd27f9a21305be2afc75cbe585ddc24e7a | 220b9dfd27f9a21305be2afc75cbe585ddc24e7a |
Published upstream
Oct 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 26, 2026
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.
Quoted source text, attributed separately from HOL analysis.