Remote code execution via Mooncake pickle deserialization
Published Apr 30, 2025 · Updated Apr 30, 2025
Unsafe deserialization in vLLM 0.6.5 through 0.8.4 allows remote attackers to execute code through Mooncake ZeroMQ messages. The mooncake_pipe.py acknowledgment and transfer receivers call recv_pyobj(), implicitly passing attacker-controlled payloads to pickle.loads(). Exploitation requires the Mooncake integration; its metadata sockets bind to all network interfaces, enabling unauthenticated code execution in the serving process.
Summary
What happened
Unsafe deserialization in vLLM 0.6.5 through 0.8.4 allows remote attackers to execute code through Mooncake ZeroMQ messages. The mooncake_pipe.py acknowledgment and transfer receivers call recv_pyobj(), implicitly passing attacker-controlled payloads to pickle.loads(). Exploitation requires the Mooncake integration; its metadata sockets bind to all network interfaces, enabling unauthenticated code execution in the serving process.
The record
- CVE
- CVE-2025-32444
- Published
- Apr 30, 2025
- Updated
- Apr 30, 2025
- Vendor
- vLLM Project
- Product
- vLLM
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 30, 2025CVE publishedPublication date reported by the CVE source.
- Apr 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.6.5, < 0.8.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo