CVE-2026-114050 · GHSA-p92p-rxj5-7p2x
vLLM: Forged multimodal UUID + P0/P1 processor-cache eviction drift: unauthenticated remote crash of the whole vLLM engine
- Risk score
- 56/100
- CVSS
- 7.5 v3.1
- Exploit chance (30 days)
- 0.2%
- Published
- 21 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 restarte…
- Affected
- vllm (pip) < 0.31.0
- Fix
- Upgrade vllm to 0.31.0 or later.
- Exploitation
- No known exploitation
Story map
At a glance
vllm: Amber, patch this week. vLLM from 0.7.3 before 0.31.0 contains an uncontrolled resource consumption vulnerability that allows remote clients to control multimodal processor parameters by supplying per-request mm_processor_kwargs. Attackers can set large image size, patch count, crop count, or frame count values in Isaac, InternVL, H2OVL, and…
The flaws
- CVE-2026-114050: VLLM: Forged multimodal UUID + P0/P1 processor-cache eviction drift: unauthenticated remote crash of the whole vLLM engine (CVSS 7.5 · EPSS 0%)
- CVE-2026-114055: VLLM : DoS via unvalidated mm_processor_kwargs in multimodal image processors (Isaac, InternVL, H2OVL, etc.) (CVSS 7.5 · EPSS 0%)
- CVE-2026-73557: VLLM: Incomplete CVE-2025-62164 remediation can be bypassed by concurrent prompt parts (CVSS 6.3)
The fix
Upgrade vllm: 0.31.0 or later on your release line
Who is exposed: vllm (pip) >= 0.7.3, < 0.31.0
Where it stands
- No known exploitation
Connects to
- Same weakness: CWE-345 (CWE-345). 45 other warnings in 30 days
Why it is Yellow
- CVSS 7.5 high
- Remotely exploitable without logging in
- On your watchlist: PyPI
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| vllm | pip | < 0.31.0 | 0.31.0 |
References
- 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
- https://github.com/advisories/GHSA-p92p-rxj5-7p2x
- https://github.com/vllm-project/vllm/pull/57833
- https://github.com/vllm-project/vllm/commit/7268f6e38ebbb3d61700f16c638c6eba0c88bb0c
- https://github.com/vllm-project/vllm/releases/tag/v0.31.0
- https://nvd.nist.gov/vuln/detail/cve-2026-114050
- https://github.com/advisories/GHSA-p92p-rxj5-7p2x
Original 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.
Last activity 23 Oct 2026. Patch Forecast updates every hour.