Remote code execution via unsafe RPC deserialization
Published Mar 20, 2025 · Updated Oct 15, 2025
Deserialization of untrusted data in vLLM 0.6.0 and earlier allows remote attackers to execute code through RPC messages. AsyncEngineRPCServer.run_server_loop passes each received message to _make_handler_coro, which invokes cloudpickle.loads without validating the serialized object. Network access to the RPC entrypoint is sufficient to run attacker-controlled code with the vLLM process privileges.
Summary
What happened
Deserialization of untrusted data in vLLM 0.6.0 and earlier allows remote attackers to execute code through RPC messages. AsyncEngineRPCServer.run_server_loop passes each received message to _make_handler_coro, which invokes cloudpickle.loads without validating the serialized object. Network access to the RPC entrypoint is sufficient to run attacker-controlled code with the vLLM process privileges.
The record
- CVE
- CVE-2024-9053
- Published
- Mar 20, 2025
- Updated
- Oct 15, 2025
- Vendor
- vLLM Project
- Product
- vLLM
- Classifications
- CWE-78, CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2025CVE publishedPublication date reported by the CVE source.
- Oct 15, 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=unspecified <=latest
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