Code execution via ZeroMQ pickle deserialization
Published May 6, 2025 · Updated May 6, 2025
Unsafe deserialization in vLLM 0.5.2 through 0.8.5.post1 allows attackers to execute code through multi-node ZeroMQ traffic. The V0 remote reader passes every message received by its ZeroMQ SUB socket directly to pickle.loads without authentication or validation. Exploitation requires tensor parallelism across multiple hosts and control of the primary host or redirected cluster traffic, granting code execution on secondary hosts.
Summary
What happened
Unsafe deserialization in vLLM 0.5.2 through 0.8.5.post1 allows attackers to execute code through multi-node ZeroMQ traffic. The V0 remote reader passes every message received by its ZeroMQ SUB socket directly to pickle.loads without authentication or validation. Exploitation requires tensor parallelism across multiple hosts and control of the primary host or redirected cluster traffic, granting code execution on secondary hosts.
The record
- CVE
- CVE-2025-30165
- Published
- May 6, 2025
- Updated
- May 6, 2025
- Vendor
- vLLM Project
- Product
- vLLM
- Classifications
- CWE-502, T1210
- Attack vector
- adjacent
- Privileges
- Unavailable
Timeline
How it unfolded
- May 6, 2025CVE publishedPublication date reported by the CVE source.
- May 6, 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.5.2, <= 0.8.5.post1
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