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.

Summary

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.

Remediation

1. Inventory every Vllm Vllm deployment, including staging.
2. Upgrade Vllm Vllm to 0.31.0.
3. Confirm the running version after the upgrade.

References

• Advisoryhttps://github.com/vllm-project/vllm/security/advisories/GHSA-p92p-rxj5-7p2x
• Advisoryhttps://www.vulncheck.com/advisories/vllm-before-0.31.0-remote-engine-crash-via-forged-multimodal-uuid