Remote code execution via unsafe pickle deserialization
Published May 20, 2025 · Updated May 20, 2025
Unsafe deserialization in vLLM 0.6.5 through 0.8.4 allows remote attackers to execute code through an exposed PyNcclPipe service. PyNcclPipe metadata reaches StatelessProcessGroup.recv_obj, which passes client-provided bytes directly to pickle.loads; TCPStore also listens on every interface instead of the configured address. Exploitation requires the V0 engine with PyNcclPipe KV-cache transfer enabled, but it requires no authentication and grants control of the server process.
Summary
What happened
Unsafe deserialization in vLLM 0.6.5 through 0.8.4 allows remote attackers to execute code through an exposed PyNcclPipe service. PyNcclPipe metadata reaches StatelessProcessGroup.recv_obj, which passes client-provided bytes directly to pickle.loads; TCPStore also listens on every interface instead of the configured address. Exploitation requires the V0 engine with PyNcclPipe KV-cache transfer enabled, but it requires no authentication and grants control of the server process.
The record
- CVE
- CVE-2025-47277
- Published
- May 20, 2025
- Updated
- May 20, 2025
- Vendor
- vLLM Project
- Product
- vLLM
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 20, 2025CVE publishedPublication date reported by the CVE source.
- May 20, 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
- PyNcclPipe malicious pickle command-execution demonstrationproof of concept · demonstrated
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