vLLM: Insecure deserialization via multimodal shared memory (CVE-2026-115912)
An authenticated caller can place forged shared-memory address and monotonic_id values in public multimodal features.kwargs_data, allowing arbitrary Python execution on vLLM worker nodes via pickle.loads().
CVE search metadata
CVE search record: CVE-2026-115912. Severity: high. CVSS: 7.5. KEV: no. Product: vLLM (< 0.32.0). Brief: vLLM: Insecure deserialization via multimodal shared memory (CVE-2026-115912). Brief link: https://feed.craftedsignal.io/briefs/2026-10-vllm-insecure-deserialization/
Triage facts
Revision 1- Applicability
- vLLM (< 0.32.0)
- Evidence
- Unknown
- Severity
- High
- Sources
- 1 public source
- Freshness
- Revision 1Oct 26, 17:45 UTC
- Vulnerabilities
- 1 CVE
- Source quality
- A2Roughly even chance
In vLLM versions 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 these values and pass attacker-selected bytes to pickle.loads(), allowing arbitrary Python execution even when insecure serialization is disabled.