WebSocket frames keep reaching the WebSock after a server-initiated close in Bandit
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.
- Products
- bandit
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-110314
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 08:58 UTC · Revision 1
Source evidence
WebSocket frames keep reaching the WebSock after a server-initiated close in Bandit
core-cve · Original sourcePublished 26 Oct 2026, 13:31 UTC
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.
cve:CVE-2026-110314
bandit
Fixed versions: Not specified
bandit
Fixed versions: Not specified
Complete source record
{
"id": "8ecdf0c5015f41ccead2a38a63a5c0e57ea66a9aa391c354e63fb7f4bcb3f316",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-110314",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "WebSocket frames keep reaching the WebSock after a server-initiated close in Bandit",
"summary": "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.",
"evidence": "cve:CVE-2026-110314",
"products": [
{
"name": {
"value": "bandit",
"evidence": "/containers/cna/affected/0/product"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": []
},
{
"name": {
"value": "bandit",
"evidence": "/containers/cna/affected/1/product"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "CVE-2026-110314",
"aliases": [
"CVE-2026-110314"
],
"metrics": [
{
"format": "CVSS",
"cvssV4_0": {
"Safety": "NOT_DEFINED",
"version": "4.0",
"Recovery": "NOT_DEFINED",
"baseScore": 6.3,
"Automatable": "NOT_DEFINED",
"attackVector": "NETWORK",
"baseSeverity": "MEDIUM",
"valueDensity": "NOT_DEFINED",
"vectorString": "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",
"providerUrgency": "NOT_DEFINED",
"userInteraction": "NONE",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"privilegesRequired": "NONE",
"subIntegrityImpact": "NONE",
"vulnIntegrityImpact": "LOW",
"subAvailabilityImpact": "NONE",
"vulnAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"affected": [
{
"cpes": [
"cpe:2.3:a:mtrudel:bandit:*:*:*:*:*:*:*:*"
],
"repo": "https://github.com/mtrudel/bandit",
"vendor": "mtrudel",
"product": "bandit",
"versions": [
{
"status": "affected",
"version": "0.5.1",
"lessThan": "1.14.0",
"versionType": "semver"
}
],
"packageURL": "pkg:hex/bandit",
"packageName": "bandit",
"collectionURL": "https://repo.hex.pm",
"defaultStatus": "unaffected"
},
{
"cpes": [
"cpe:2.3:a:mtrudel:bandit:*:*:*:*:*:*:*:*"
],
"repo": "https://github.com/mtrudel/bandit",
"vendor": "mtrudel",
"product": "bandit",
"versions": [
{
"status": "affected",
"version": "bb407f2277dcb65a58dd8cc07913a0b58a80e266",
"lessThan": "220b9dfd27f9a21305be2afc75cbe585ddc24e7a",
"versionType": "git"
}
],
"packageURL": "pkg:github/mtrudel/bandit",
"packageName": "mtrudel/bandit",
"collectionURL": "https://github.com",
"defaultStatus": "unaffected"
}
],
"modified": "2026-10-26T13:31:18.257Z",
"provider": "cve",
"references": [
"https://github.com/mtrudel/bandit/security/advisories/GHSA-2v5v-8f9v-xh85",
"https://cna.erlef.org/cves/CVE-2026-110314.html",
"https://osv.dev/vulnerability/EEF-CVE-2026-110314",
"https://github.com/mtrudel/bandit/commit/bb407f2277dcb65a58dd8cc07913a0b58a80e266",
"https://github.com/mtrudel/bandit/commit/220b9dfd27f9a21305be2afc75cbe585ddc24e7a"
],
"provider_metadata": {
"cna": {
"orgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"shortName": "EEF",
"dateUpdated": "2026-10-26T13:31:18.257Z"
}
}
},
"related_cves": [
{
"value": "CVE-2026-110314",
"evidence": "/cveMetadata/cveId"
}
],
"security_relevant": true,
"severity_evidence": "/containers/cna/metrics"
},
"source_id": "core-cve",
"document_id": 307250,
"published_at": "2026-10-26T13:31:18.257+00:00"
}