CVE-2026-114050: vLLM multimodal UUID cache identity flaw leads to engine crash
vLLM
A cache identity flaw in vLLM before version 0.31.0 enables unauthenticated attackers to desynchronize processor caches. The resulting fatal token-placeholder mismatch crashes the serving instance until a manual restart.
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
- 6.5
- EPSS
- <0.01 · top 90% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 21 Oct 2026
- last update
- 23 Oct 2026
- CVE ids
Timeline · 2
- 21 Oct 2026CVE-2026-114050: vLLM before 0.31.0 uses a client-supplied multimodal uuid verbatim as cache identity with no consistency check on cache hits,…
- 23 Oct 2026CVE-2026-114050: vLLM: Forged multimodal UUID + P0/P1 processor-cache eviction drift: unauthenticated remote crash of the whole vLLM engine
Sources · 2
Advisories and databases
- 2026-10-21CVE-2026-114050: vLLM before 0.31.0 uses a client-supplied multimodal uuid verbatim as cache identity with no consistency check on cache hits,…NVD · nvd.nist.gov/vuln/detail/CVE-2026-114050
- 2026-10-23CVE-2026-114050: vLLM: Forged multimodal UUID + P0/P1 processor-cache eviction drift: unauthenticated remote crash of the whole vLLM engineGitHub Advisory Database · github.com/advisories/GHSA-p92p-rxj5-7p2x
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 vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- 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-23 22:00Z
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-114050: vLLM multimodal UUID cache identity flaw leads to engine crash https://gcdradar.vercel.app/incidents/cve-2026-114050-vllm-multimodal-uuid-cache-identity-flaw-lea · AIR-2026-1453 · 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-114050 - CVSS: 6.5 ## Summary A cache identity flaw in vLLM before version 0.31.0 enables unauthenticated attackers to desynchronize processor caches. The resulting fatal token-placeholder mismatch crashes the serving instance until a manual restart. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-10-23: CVE-2026-114050: vLLM: Forged multimodal UUID + P0/P1 processor-cache eviction drift: unauthenticated remote crash of the whole vLLM engine (https://github.com/advisories/GHSA-p92p-rxj5-7p2x) - 2026-10-21: CVE-2026-114050: vLLM before 0.31.0 uses a client-supplied multimodal uuid verbatim as cache identity with no consistency check on cache hits,… (https://nvd.nist.gov/vuln/detail/CVE-2026-114050) ## Sources - 2026-10-21 NVD: CVE-2026-114050: vLLM before 0.31.0 uses a client-supplied multimodal uuid verbatim as cache identity with no consistency check on cache hits,… https://nvd.nist.gov/vuln/detail/CVE-2026-114050 - 2026-10-23 GitHub Advisory Database: CVE-2026-114050: vLLM: Forged multimodal UUID + P0/P1 processor-cache eviction drift: unauthenticated remote crash of the whole vLLM engine https://github.com/advisories/GHSA-p92p-rxj5-7p2x Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed6.9vLLM CVE-2026-126395: vLLM information disclosure vulnerability in sanitize_message()
Patch now · Disclosed · Patched · since 13 Nov 2026 · CVE-2026-126395
AI - closed7.1vLLM CVE-2026-126399: vLLM resource exhaustion vulnerability via video frame limits bypass
Patch now · Disclosed · Patched · since 13 Nov 2026 · CVE-2026-126399
AI - closed8.2vLLM CVE-2026-126398: vLLM reachable assertion vulnerability in GPUModelRunner._init_xdrope_positions
Patch now · Disclosed · Patched · since 13 Nov 2026 · CVE-2026-126398
AI - closed6.9vLLM CVE-2026-126394: vLLM resource exhaustion vulnerability in OpenCVDynamicOpenPanguVideoBackend
Patch now · Disclosed · Patched · since 13 Nov 2026 · CVE-2026-126394
AI - closed8.7vLLM CVE-2026-126397: vLLM quadratic CPU work vulnerability in Cohere2 Vision multimodal preprocessing
Patch now · Disclosed · Patched · since 13 Nov 2026 · CVE-2026-126397
AI - closed6.9vLLM CVE-2026-126396: vLLM resource exhaustion vulnerability in MiniMax M3 VL video processor
Patch now · Disclosed · Patched · since 13 Nov 2026 · CVE-2026-126396
AI