CVE-2026-114054: vLLM cache aliasing vulnerability exposes processed media and KV state
vLLM
A cache aliasing vulnerability in vLLM before version 0.31.0 lets authenticated attackers collide shared cache keys. This permits unauthorized retrieval of another request's cached media or key-value states.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 7.1
- EPSS
- <0.01 · top 80% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 21 Oct 2026
- last update
- 21 Oct 2026
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2026-10-21CVE-2026-114054: vLLM before 0.31.0 contains a cache aliasing vulnerability that allows authenticated attackers to collide shared cache keys by…NVD · nvd.nist.gov/vuln/detail/CVE-2026-114054
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerabilityData leak
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- mitre atlas
- no technique for these categories
- tags
- vllm
- dates
- happened 21 Oct 2026 · first reported 21 Oct 2026
- origin
- NVDVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-21 05:04Z · updated 2026-10-21 05:04Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2026-114054: vLLM cache aliasing vulnerability exposes processed media and KV state https://gcdradar.vercel.app/incidents/cve-2026-114054-vllm-cache-aliasing-vulnerability-exposes-pr · AIR-2026-1452 · closed 2026-10-21 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-10-21 - AI role: Attack on AI - Products: vLLM - CVE ids: CVE-2026-114054 - CVSS: 7.1 ## Summary A cache aliasing vulnerability in vLLM before version 0.31.0 lets authenticated attackers collide shared cache keys. This permits unauthorized retrieval of another request's cached media or key-value states. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-10-21: CVE-2026-114054: vLLM before 0.31.0 contains a cache aliasing vulnerability that allows authenticated attackers to collide shared cache keys by… (https://nvd.nist.gov/vuln/detail/CVE-2026-114054) ## Sources - 2026-10-21 NVD: CVE-2026-114054: vLLM before 0.31.0 contains a cache aliasing vulnerability that allows authenticated attackers to collide shared cache keys by… https://nvd.nist.gov/vuln/detail/CVE-2026-114054 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed8.8vLLM CVE-2026-116176: vLLM server-side request forgery leads to NCCL unique_id and KV-cache leakage
Patch now · Disclosed · since 25 Oct 2026 · CVE-2026-116176
AI - closed5.3vLLM CVE-2026-73558: vLLM data leakage vulnerability in activation kernels
Patch now · Disclosed · since 13 Aug 2026 · updated 8 Sep 2026 · CVE-2026-73558
AI - closed5.3vLLM CVE-2026-73555: Information disclosure vulnerability in vLLM request validation handling
Patch now · Disclosed · since 13 Aug 2026 · updated 4 Sep 2026 · CVE-2026-73555
AI - closed7.5vLLM CVE-2025-30202: Data Exposure via ZeroMQ in Multi-Node vLLM Deployment
Patch now · Disclosed · since 29 Apr 2025 · updated 30 Apr 2025 · CVE-2025-30202
AI - closedMicrosoft 365 Agents SDK CVE-2026-109485 Microsoft 365 Agents SDK Information Disclosure Vulnerability
Patch now · Disclosed · since 10 Nov 2026 · CVE-2026-109485
AI - liveSGLang SGLang RCE Exploit Breaches NEAR AI, Steals Data From 18 Agents
Breaches & attacks · Exploited · since 8 Nov 2026
AI