# CVE-2026-111392: SGLang through 0.5.21 KV Cache Poisoning via mm_hashes in /generate

> Remote attackers can poison KV cache entries in SGLang to disclose other users' image content or corrupt responses via the /generate endpoint.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-fgff-m398-2gh5

## What is CVE-2026-111392?

CVE-2026-111392 is a medium-severity vulnerability in sgl-project sglang, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SGLang through 0.5.21 trusts caller-supplied mm_hashes values as the multimodal prefix-cache key, allowing remote attackers to poison cached KV entries across requests. Attackers can send a different image under a known or predicted hash via /generate to disclose another request's image content or corrupt victims' responses.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

No fix has been published for CVE-2026-111392 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111392 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111392 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111392 is a medium-severity vulnerability in sgl-project sglang, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111392 exists.

Affected product: sgl-project sglang. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-111392/ (Markdown: https://insights.sbomify.com/CVE-2026-111392/index.md)
```

## Sources

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

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