# CVE-2026-110314: WebSocket frames keep reaching the WebSock after a server-initiated close in Bandit


- **Severity:** Medium 6.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** EEF-CVE-2026-110314, GHSA-2v5v-8f9v-xh85, UBUNTU-CVE-2026-110314

## What is CVE-2026-110314?

CVE-2026-110314 is a medium-severity vulnerability in mtrudel bandit, published on 26 Oct 2026. 

### Official 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.

Weakness: CWE-602 (Client-Side Enforcement of Server-Side Security)

## Which versions are affected by CVE-2026-110314?

1 open source package ship an affected version, including bandit.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bandit` | Hex | From 0.5.1 | 1.14.0 |

## How do I fix CVE-2026-110314?

Upgrade bandit to 1.14.0 or later.

## Is CVE-2026-110314 being exploited?

There is no known exploitation of CVE-2026-110314 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110314 and fix it if it is affected.

What it is: CVE-2026-110314 is a medium-severity vulnerability in mtrudel bandit, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-110314 in the wild and no public exploit code.

Affected packages and fixed versions:
- bandit (Hex): affected from 0.5.1; fixed in 1.14.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110314/ (Markdown: https://insights.sbomify.com/CVE-2026-110314/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110314
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110314
- OSV: https://osv.dev/vulnerability/CVE-2026-110314

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110314/
Summaries are generated and may contain mistakes; the official description above is the record.