CVE-2026-115912

LOWCVSS 7.5 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD 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.

Back to dashboard

0.0/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-502

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

1 mentions across 1 observed day

What's happening

1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d

Referenced assets2 URLs

By indicator

Full discourse1 post

ATIK@atikbytes19h
1/ vLLM users: 0.32.0 fixes 8 CVEs published yesterday. The worst (CVE-2026-115912): with the shared-memory multimodal cache on, a logged-in caller can forge a handle so a worker runs pickle.loads() on their bytes. That's code execution, even with insecure serialization turned off. 2/ Also fixed: - An EPS file labelled as a PNG can reach Ghostscript on the host - Untrusted Jinja chat templates with no time or memory limit - Several requests that crash the engine for every user If you share a vLLM server, upgrade to 0.32.0. https://vibevulns.com/advisories/cve-2026-115912-vllm-0-32-pickle-rce-eps-images-and-engine-crashes/ 3/ Building multi-user agents on Mem0? CVE-2026-116575: a run_id like "proj-x&user_id=alice" maps to Alice's session, so one user can read another's recent messages. Fixed in mem0ai 2.0.18 (pip) and 3.1.6 (npm). https://vibevulns.com/advisories/cve-2026-116575-mem0-cross-tenant-conversation-leak/
0000019
661 followersView on X

Explore more

Back to dashboard