CVE-2025-29783 json
vLLM Allows Remote Code Execution via Mooncake Integration
published 2025-03-19 19 mo ago modified 2026-08-07 3 mo ago also EUVD-2025-6725 , GHSA-x3m8-f7g5-qhm7 , PYSEC-2025-63
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. When vLLM is configured to use Mooncake, unsafe deserialization exposed directly over ZMQ/TCP on all network interfaces will allow attackers to execute remote code on distributed hosts. This is a remote code execution vulnerability impacting any deployments using Mooncake to distribute KV across distributed hosts. This vulnerability is fixed in 0.8.0.
Patch / fix
- pypi vllm 0.8.0
- vllm-project vllm 0.8.0
- vllm vllm 0.8.0
- github.com/vllm-project/vllm@288ca11 commit
- github.com/vllm-project/vllm#14228 pull request
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-29783 updated cvss 10.0
vllm: vLLM Allows Remote Code Execution via Mooncake Integration
-
Red Hat Enterprise Linux AI (RHEL AI) rhelai1/ui-rhel9, rhelai1/bootc-amd-rhel9, rhelai1/bootc-intel-rhel9, rhelai1/bootc-nvidia-rhel9, rhelai1/bootc-azure-amd-rhel9, rhelai1/instructlab-amd-rhel9, +6 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 19 mo ago
Exploit prediction
0.73% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.0 | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | vllm | >=0.6.5, <0.8.0 |
0.8.0 |
Affected products
- vllm-project vllm
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
github.com
/vllm-project/vllm/pull/14228
web, issue-tracking, vendor-advisory, report
-
github.com
/vllm-project/vllm/commit/288ca110f68d23909728627d3100e5a8db820aa2
web, patch
-
github.com
/vllm-project/vllm/security/advisories/GHSA-x3m8-f7g5-qhm7
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-29783
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2025-63.yaml
web
-
github.com
/vllm-project/vllm
package
Sources
- CVE List CVE-2025-29783
- GitHub Advisory GHSA-x3m8-f7g5-qhm7
- NVD CVE-2025-29783
- OSV PYSEC-2025-63
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.