CVE-2026-110314

WebSocket frames keep reaching the WebSock after a server-initiated close in Bandit

MEDIUM
6.3
CVSS Score
Published: October 26, 2026 at 01:31 PM UTC
Updated: October 26, 2026 at 04:59 PM UTC
1 product affected across 1 vendorBandit

Using bandit by mtrudel?

Get instant alerts when new vulnerabilities affect bandit - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.3
Exploit prediction
EPSS 0.4%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0.5.1bb407f2277dcb65a58dd8cc07913a0b58a80e266

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

6.3MEDIUMEEF
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-602

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card