High 7.5Published Oct 20, 2026

CVE-2026-114050vLLM before 0.31.0 Remote Engine Crash via Forged Multimodal UUID

Updated under an hour ago (Oct 28, 2026, 7:20 AM ET)

Does this affect you?

It affects vllm-project vllm. Add what you run to find out whether that includes you.

EPSS puts the chance of exploitation in the next 30 days at 0.20%, higher than 10% of scored CVEs.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for vllm-project vllm

Exploited in the last 30 days

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.

CVSS: 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE): CWE-345
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): 0.20% (percentile 10)
Assigned by: VulnCheck
NVD analysis: Awaiting Analysis
Record last updated: Oct 21, 2026
First seen by InfoSec Signals: Oct 20, 2026

Affected products

Affected products

vllm-project vllm vllm_project:vllm (from the name)	before 0.31.0; 0.31.0 not affected	CNA record

References

References

https://github.com/vllm-project/vllm/security/advisories/GHSA-p92p-rxj5-7p2x	vendor-advisory
https://www.vulncheck.com/advisories/vllm-before-0.31.0-remote-engine-crash-via-forged-multimodal-uuid	third-party-advisory

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.