PT-2026-123296
CVE-2026-110314
·
Published
2026-10-26
·
Updated
2026-10-26
Description by
CVSS 4.0
6.3
MediumMetricsAV: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
Name of the Vulnerable Software and Affected Versions
bandit versions 0.5.1 through 1.13.x
Description
An issue in the WebSocket connection handling allows a remote client to continue executing handler code after the server has attempted to stop the connection. This occurs because when a callback returns
{:stop, ...}, the Bandit.WebSocket.Connection process enters a :closing state but continues to process incoming data frames and messages. The functions handle frame/3 and handle info/3 do not verify the connection state, allowing frames to reach handle in/2 and messages to reach handle info/2 until the client sends a Close frame, the TCP connection drops, or an idle timeout occurs. This can lead to the bypass of authorization checks in init/1 or the evasion of session terminations such as kicks or bans, potentially allowing unauthorized access to administrative actions.Recommendations
Update bandit to version 1.14.0 or later.
As a temporary workaround, mark the WebSock state as stopped whenever a callback returns
{:stop, ...}, and ensure handle in/2 and handle info/2 return {:ok, state} without performing any actions while that mark is set. Found an issue in the description? Have something to add? Feel free to write us 👾