vLLM cross-instance image cache ID collision vulnerability and its fix
Automated summary · Based on collected summaries; not individually verified
Prepared by HotAI
What happened
vLLM suffers from a cross-instance image cache collision issue when sharing external KV cache across multiple servers: when prefix cache and image processing cache are both disabled, each server counts image labels starting from 1, causing different images to collide on the same key in shared cache. The second server hits this collision and returns cached data for another image, appearing as a normal cache hit without errors. The fix involves having each server include its own random component in image labels so cross-server labels remain distinct; the relevant PR is #67461.
Background
What is a pull request? Diffs, reviews, checks, and merge state
A pull request proposes merging one branch into another and collects review, discussion, and checks. It differs from a commit and does not establish merge or deployment. AI-created PRs still need diff and test review under project rules. User availability depends on release and live verification.
Reading notes
The event summary comes from collected excerpts. Background passages quote existing HotAI articles to explain terms and do not establish new facts about this event. Check the original sources for product results, conditions and subsequent updates.
Original source
Sources and collection timeline
| Source | Report title | Original publication time | Collected by HotAI |
|---|---|---|---|
| x.com | vLLM cross-instance image cache ID collision vulnerability and its fix | 2026-11-14 03:13 | 2026-11-14 03:37 |