CVE-2026-105753
What it is
vLLM is an inference and serving engine for large language models. Prior to 0.28.0, the default mirrored multimodal LRU cache can commit a media hash in the frontend sender cache during multimodal rendering and before engine admission, while the engine receiver cache never receives the payload if that request is rejected. A later request reusing the same media hash causes MultiModalProcessorSenderCache to send no payload and MultiModalReceiverCache to reach an assertion with the message "Expected a cached item," producing a shared-service availability failure. This issue is fixed in version 0.28.0.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.4% in the next 30 days (EPSS).
- Severity: 6.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.4% · EPSS, next 30 days
- Weakness
- CWE-617
- Record status
- Analyzed
Affected
- Vllm < 0.28.0
Attack profile CVSS 3.1 · 6.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-105753.md and follow it. Check whether this project is affected by CVE-2026-105753. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/vllm-project/vllm/commit/396204230423b7cc6798300926b8fa30190d26a9
- https://github.com/vllm-project/vllm/pull/46747
- https://github.com/vllm-project/vllm/pull/51897
- https://github.com/vllm-project/vllm/releases/tag/v0.28.0
- https://github.com/vllm-project/vllm/security/advisories/GHSA-ph3r-5jfg-f84f
References
- https://github.com/vllm-project/vllm/commit/396204230423b7cc6798300926b8fa30190d26a9
- https://github.com/vllm-project/vllm/pull/46747
- https://github.com/vllm-project/vllm/pull/51897
- https://github.com/vllm-project/vllm/releases/tag/v0.28.0
- https://github.com/vllm-project/vllm/security/advisories/GHSA-ph3r-5jfg-f84f