vLLM before 0.31.0 contains a cache aliasing vulnerability that allows authenticated attackers to collide shared cache keys by supplying caller-controlled values such as EXIF ImageID or cache_salt....

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0027, the 19th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 21 Oct 2026, 01:17 UTC Confirmed by NVD
2. 4 Nov 2026, 11:00 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-rh6f-3x46-j33q
• OSV: GHSA-rh6f-3x46-j33q
• github.com/vllm-project/vllm/security/advisories/GHSA-rh6f-3x46-j33q
• www.vulncheck.com/advisories/vllm-before-0.31.0-cross-request-cache-aliasing-via-exif-imageid-and-prefix-cache-keys

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.