Skip to main content
VulnerabilityPublished

CVE-2026-115912: vllm · Deserialization of Untrusted Data

Affects vllmSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 0.32.0 soon.

Data as of 26 Oct 2026, 19:57 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.32.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade vllm to 0.32.0.

Affected software

ProductAffectedFixed in
vllm-projectvllmAffected
  • <0.32.0
Fixed in
  • 0.32.0
PyPIvllmpkg:pypi/vllmOther threatsAffected
  • <0.32.0
Fixed in
  • 0.32.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.32.0 or later, where this vulnerability is fixed. No other mitigations are specified. Since this is an authenticated attack vector, restricting access to trusted users reduces risk but does not eliminate it. Patch status is confirmed fixed in 0.32.0.

Description

vLLM is an inference and serving engine for large language models. Prior to 0.32.0, an authenticated caller can place forged shared-memory address and monotonic_id values in public multimodal features.kwargs_data. In scale-out deployments with shared-memory multimodal caching enabled, workers trust those values and pass attacker-selected bytes to pickle.loads(), allowing arbitrary Python execution even when insecure serialization is disabled. This issue is fixed in version 0.32.0.

References

Community reviews

Loading reviews…