Skip to main content
VulnerabilityPublished

CVE-2026-105753: vllm · Reachable Assertion

Affects vllmSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 0.28.0 when convenient.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.28.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade vllm and vllm-project/vllm to 0.28.0.

Affected software

ProductAffectedFixed in
vllm-projectvllmAffected
  • <0.28.0
Fixed in
  • 0.28.0
GitHubvllm-project/vllmpkg:github/vllm-project/vllmOther threatsAffected
  • <0.28.0
Fixed in
  • 0.28.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade vLLM to version 0.28.0 or later, where this issue is fixed. No other mitigations are indicated.

Description

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.

References

Community reviews

Loading reviews…