# vLLM: Mirrored multimodal IPC caches desync after a rejected request — a later request reusing the same media hash trips a receiver assertion in the engine core

Advisory record · `GHSA-ph3r-5jfg-f84f`

- **Identifiers:** `GHSA-ph3r-5jfg-f84f` · `CVE-2026-105753` · `PYSEC-2026-4197`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-617](https://cwe.mitre.org/data/definitions/617.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 6 Oct 2026
- **Updated:** 8 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 6 Oct 2026, 00:02 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `vllm` (PyPI): affected `<0.28.0`; fixed in `0.28.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> vLLM versions before 0.28.0 are affected. When a multimodal request is rejected after its media has been rendered and hashed, the frontend cache can record media that the engine core never received. A later request reusing the same media hash can then trigger an assertion in the engine core, which affects availability for a shared serving instance; the source describes no code execution or data disclosure. An attacker needs only to send multimodal requests with the default cache configuration. Upgrade to vLLM 0.28.0 or later, which is the listed fixed version.

Written 1 Nov 2026.

## 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

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0043, the 37th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:08 UTC: First seen by agentprime
- 31 Oct 2026, 14:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-ph3r-5jfg-f84f)

## Sources

- [GitHub Advisory Database: GHSA-ph3r-5jfg-f84f](https://github.com/advisories/GHSA-ph3r-5jfg-f84f)
- [OSV: GHSA-ph3r-5jfg-f84f](https://osv.dev/vulnerability/GHSA-ph3r-5jfg-f84f)
- <https://github.com/vllm-project/vllm/security/advisories/GHSA-ph3r-5jfg-f84f>
- <https://github.com/vllm-project/vllm/pull/46747>
- <https://github.com/vllm-project/vllm/pull/51897>
- <https://github.com/vllm-project/vllm/commit/396204230423b7cc6798300926b8fa30190d26a9>
- <https://github.com/vllm-project/vllm>
- <https://github.com/vllm-project/vllm/releases/tag/v0.28.0>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-ph3r-5jfg-f84f>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-ph3r-5jfg-f84f/>. Everything for agents: <https://agentprime.io/llms.txt>.