Vulnerabilities

Vulnerability · CVE-2026-105754

vLLM: Scale-out disaggregated multimodal transport trusts caller-supplied features

Published Oct 5, 2026 · catalog updated Oct 15, 2026 · vLLM: Scale-out disaggregated multimodal

Check if you run it

No confirmed exploitation is on record for CVE-2026-105754. EPSS is 0.27%. Act only if a listed version of vLLM: Scale-out disaggregated multimodal is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (vLLM: Scale-out disaggregated multimodal).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium6.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.27%
Remediation
Advisory link
Affected products
PyPI vllm

## Affected - **Ecosystem / package:** pip / - **Affected versions:** vLLM ≤ 0.25.1 (confirmed on 0.25.1, commit [ ](https://github.com/vllm-project/vllm/tree/752a3a504485790a2e8491cacbb35c137339ad34)). The lower bound predates 0.25.1; maintainers can confirm how far back the scale-out transport path reaches. ## Summary vLLM's disaggregated **scale-out** transport splits a multimodal request into a trusted render step ( ) and a separate generate step ( ). The generate route decodes a caller-supplied object — serialized encoder tensors ( ), multimodal hashes ( ), placeholder ranges ( ), and the internal field-processor selection — and forwards it into the engine **as if it had come from the trusted renderer**, with no rebinding to (or validation against) the active model's renderer contract. Because the two routes are ordinary auth-guarded HTTP endpoints (the prefix is registered by default on generate-capable servers), any authenticated caller can submit an otherwise-valid render body with a single forged field. Depending on which field is forged, this produces: - an **engine-fatal crash** of the shared EngineCore process (denial of service), reproduced as a CUDA illegal-memory-access, a post-admission rank-mismatch , and a hard — three independent forged fields (sites 1, 2, 3); - **silent cross-request encoder-cache poisoning / disclosure** of shared encoder state when the cache-key hash is not bound to the payload (site 4); - **transport-level integrity loss** when sparse placeholder masks are dropped during render-to-generate replay (site 5). All five share one root cause and one fix shape: the reconstructed multimodal state on the scale-out path is trusted without being rebound to, and validated against, the active model's renderer output before it reaches the engine. These sites are distinct from prior multimodal hardening. Site 1 survives [GHSA-wv77-2vpf-vmmg](https://github.com/vllm-project/vllm/security/advisories/GHSA-wv77-2vpf-vmmg) (that fix validates ful

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • PyPI vllm0 → 0.30.0

How to fix CVE-2026-105754

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-105754. EPSS is 0.27%. Act only if a listed version of vLLM: Scale-out disaggregated multimodal is installed.

Which versions are affected?

Compare what you have installed with 0 → 0.30.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-1284; CWE-20: Improper Input Validation; CWE-617. EPSS 0.27%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 5, 2026 · GitHub Advisory Database

    Detected

    ## Affected - **Ecosystem / package:** pip / - **Affected versions:** vLLM ≤ 0.25.1 (confirmed on 0.25.1, commit [ ](https://github.com/vllm-project/vllm/tree/752a3a504485790a2e8491cacbb35c137339ad34)). The lower bound predates 0.25.1; maintainers can confirm how far back the scale-out transport path reaches. ## Summary vLLM's disaggregated **scale-out** transport splits a multimodal request into

  2. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    vllm fixed in 0.30.0

  3. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    vllm fixed in 0.30.0

  4. Oct 15, 2026 · GitHub Advisory Database

    Updated

    ## Affected - **Ecosystem / package:** pip / - **Affected versions:** vLLM ≤ 0.25.1 (confirmed on 0.25.1, commit [ ](https://github.com/vllm-project/vllm/tree/752a3a504485790a2e8491cacbb35c137339ad34)). The lower bound predates 0.25.1; maintainers can confirm how far back the scale-out transport path reaches. ## Summary vLLM's disaggregated **scale-out** transport splits a multimodal request into

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.