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

> Attackers can execute arbitrary code by sending malicious pickle data to the RPC server, affecting users of the vllm library.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 15 Oct 2025
- **Also known as:** GHSA-cj47-qj6g-x7r4, PYSEC-2025-222

## What is CVE-2024-9053?

CVE-2024-9053 is a critical unsafe deserialization vulnerability in vllm-project/vllm, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-9053?

3 open source packages ship an affected version, including vllm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vllm` | PyPI | All versions to 0.6.0 | None |
| `vllm` | PyPI | All versions to 0.6.0 | None |
| `vllm` | PyPI | All versions to 0.6.0 | None |

Products: Vllm-Project Vllm.

## How do I fix CVE-2024-9053?

No fix has been published for CVE-2024-9053 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-9053 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9053 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-9053 and fix it if it is affected.

What it is: CVE-2024-9053 is a critical unsafe deserialization vulnerability in vllm-project/vllm, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9053 exists.

Affected packages and fixed versions:
- vllm (PyPI): affected all versions up to 0.6.0; no fix listed
- vllm (PyPI): affected all versions up to 0.6.0; no fix listed
- vllm (PyPI): affected all versions up to 0.6.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-9053/ (Markdown: https://insights.sbomify.com/CVE-2024-9053/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-9053
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-9053
- OSV: https://osv.dev/vulnerability/CVE-2024-9053

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-9053/
Summaries are generated and may contain mistakes; the official description above is the record.