Advisory

GHSA-x3m8-f7g5-qhm7

Also known as: CVE-2025-29783, PYSEC-2025-63

Summary

vLLM Allows Remote Code Execution via Mooncake Integration

Details

Summary
When vLLM is configured to use Mooncake, unsafe deserialization exposed directly over ZMQ/TCP will allow attackers to execute remote code on distributed hosts.

Details

  1. Pickle deserialization vulnerabilities are well documented.
  2. The mooncake pipe is exposed over the network (by design to enable disaggregated prefilling across distributed environments) using ZMQ over TCP, greatly increasing exploitability. ~~Further, the mooncake integration opens these sockets listening on all interfaces on the host, meaning it can not be configured to only use a private, trusted network.~~

Only sender_socket and receiver_ack are allowed to be accessed publicly, while the data actually decompressed by pickle.loads() comes from recv_bytes. Its interface is defined as self.receiver_socket.connect(f\"tcp://{d_host}:{d_rank_offset + 1}\"), where d_host is decode_host, a locally defined address 192.168.0.139,from mooncake.json (https://github.com/kvcache-ai/Mooncake/blob/main/doc/en/vllm-integration-v0.2.md?plain=1#L36).

  1. The root problem is `recv_tensor()` calls `_recv_impl` which passes the raw network bytes to pickle.loads(). Additionally, it does not appear that there are any controls (network, authentication, etc) to prevent arbitrary users from sending this payload to the affected service.

Impact
This is a remote code execution vulnerability impacting any deployments using Mooncake to distribute KV across distributed hosts.

Remediation
This issue is resolved by https://github.com/vllm-project/vllm/pull/14228

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2025-03-19 15:55 UTC
Modified
2026-08-07 08:11 UTC

Affected packages and fixes

vllm

PyPI · All systems

Affected

  • introduced 0.6.5, fixed 0.8.0 (ecosystem)

Fixed versions

0.8.0

Fix

  • Fixed version 0.8.0
    pip install --upgrade vllm==0.8.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences