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.
{
"cna_assigner": "EEF",
"cwe_ids": [
"CWE-602"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/110xxx/CVE-2026-110314.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "bb407f2277dcb65a58dd8cc07913a0b58a80e266"
},
{
"fixed": "220b9dfd27f9a21305be2afc75cbe585ddc24e7a"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"introduced": "0.5.1"
},
{
"fixed": "1.14.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"fixed": "bb407f2277dcb65a58dd8cc07913a0b58a80e266"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "220b9dfd27f9a21305be2afc75cbe585ddc24e7a"
}
],
"source": "REFERENCES_COMMIT"
}
]
}