vllm-project · vLLM · published 2026-10-21
CVE-2026-114050vLLM before 0.31.0 Remote Engine Crash via Forged Multimodal UUID
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-114050 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 11% of all CVEs. This vLLM vulnerability: CVSS 7.1 (v4.0). Fixed upstream in vLLM 0.31.0. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in vLLM 0.31.0.
Patch events
AI toolingvLLM
vLLM security release: 0.31.0
Upgrade to
0.31.0Why: Vendor security release for server software (most severe: CVE-2026-114052).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (11th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.1 (v4.0)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- vllm-project vllm
0to before0.31.0(affected)0.31.0(unaffected)
Description (from the CVE record)#
vLLM before 0.31.0 uses a client-supplied multimodal uuid verbatim as cache identity with no consistency check on cache hits, allowing engine crashes. Unauthenticated attackers can desynchronize the P0/P1 processor caches to trigger a fatal token-placeholder mismatch, killing the entire serving instance until restarted.
Quoted from the CVE Program record.