Quick answers
- Is CVE-2026-105754 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105754 being exploited in the wild.
- How severe is CVE-2026-105754?
- Medium severity, with a CVSS score of 6.5, published 5 October 2026.
- Which products and versions are affected?
- vllm (PyPI) < 0.30.0, ECOSYSTEM:introduced=0,fixed=0.30.0; Vllm before 0.30.0.
- Is there a fix for CVE-2026-105754?
- Yes. vllm (PyPI): upgrade to 0.30.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105754 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105754?
- Check whether you run vllm (PyPI) or Vllm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- vllm (PyPI): upgrade to 0.30.0 or later
pip install "vllm>=0.30.0"
Technical details
The /inference/v1/generate endpoint in vLLM's disaggregated scale-out path accepts caller-supplied multimodal data in features.kwargs_data, features.mm_hashes, and features.mm_placeholders fields without proper validation or rebinding to the active model renderer contract. An unauthenticated network attacker can supply forged grid geometry, field types, or non-positive placeholder lengths to crash the EngineCore; known content hashes can be used to poison or retrieve cross-request encoder-cache state; and missing sparse placeholder masks can alter transport semantics. The vulnerability was patched by adding input validation before engine handoff.
Affected products
- vLLM vLLM before 0.30.0
Identifiers
- CVE-2026-105754
- GHSA-ph72-cqr5-qpp7
- PYSEC-2026-4309
Timeline
- 2026-10-05: disclosed