| Component | vLLM |
| Severity | high (CVSS 7.5) |
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| Published (NVD) | 2026-10-21 |
| Affected versions | < 0.31.0 from the CVE Program record written by the CNA that assigned the CVE |
| Fixed in | 0.31.0 |
| Weakness | CWE-345 |
| CISA KEV | not listed |
NVD description
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.
What to do
- Upgrade vLLM to
0.31.0or later. - Do not expose the component's API or UI to the internet without authentication in front of it.
Sources
- NVD: CVE-2026-114050
- https://github.com/vllm-project/vllm/security/advisories/GHSA-p92p-rxj5-7p2x
- https://www.vulncheck.com/advisories/vllm-before-0.31.0-remote-engine-crash-via-forged-multimodal-uuid