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

> An attacker can execute arbitrary code on the victim's machine by sending a malicious payload to the MessageQueue due to unsafe pickle deserialization.

- **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:** 20 Mar 2025
- **Also known as:** GHSA-5vqr-wprc-cpp7, PYSEC-2026-566

## What is CVE-2024-11041?

CVE-2024-11041 is a critical unsafe deserialization vulnerability in Vllm 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 v0.6.2 contains a vulnerability in the MessageQueue.dequeue() API function. The function uses pickle.loads to parse received sockets directly, leading to a remote code execution vulnerability. An attacker can exploit this by sending a malicious payload to the MessageQueue, causing the victim's machine to execute arbitrary code.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

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.2 | None |
| `vllm` | PyPI | All versions to 0.6.2 | None |
| `vllm` | PyPI | All versions to 0.6.2 | None |

Products: Vllm Vllm.

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

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

## Is CVE-2024-11041 being exploited?

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

## Other vulnerabilities in Vllm Vllm

- [CVE-2025-32444](https://insights.sbomify.com/CVE-2025-32444/): vLLM Vulnerable to Remote Code Execution via Mooncake Integration (critical 10.0)
- [CVE-2026-22778](https://insights.sbomify.com/CVE-2026-22778/): vLLM leaks a heap address when PIL throws an error (critical 9.8)
- [CVE-2025-47277](https://insights.sbomify.com/CVE-2025-47277/): vLLM Allows Remote Code Execution via PyNcclPipe Communication Service (critical 9.8)
- [CVE-2026-48746](https://insights.sbomify.com/CVE-2026-48746/): vLLM: OpenAI auth bypass (critical 9.1)
- [CVE-2025-29783](https://insights.sbomify.com/CVE-2025-29783/): vLLM Allows Remote Code Execution via Mooncake Integration (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-11041 is a critical unsafe deserialization vulnerability in Vllm 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-11041 exists.

Affected packages and fixed versions:
- vllm (PyPI): affected all versions up to 0.6.2; no fix listed
- vllm (PyPI): affected all versions up to 0.6.2; no fix listed
- vllm (PyPI): affected all versions up to 0.6.2; 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-11041/ (Markdown: https://insights.sbomify.com/CVE-2024-11041/index.md)
```

## Sources

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

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