8

CVE-2025-30165: vllm-project vllm Deserialization of Untrusted Data

CVSS: 8.0v3.1HighAnalyzed
AliasesGHSA-9pcc-gvx5-r5wmPYSEC-2026-2017
Published 06-05-2025Last modified 06-05-2025

Vulnerability summary

CVE-2025-30165 is a high (CVSS 8.0) Deserialization of Untrusted Data vulnerability in vllm-project vllm. EPSS estimates a 0.56% chance of exploitation in the next 30 days, higher than 45.8% of scored vulnerabilities.

Overall risk
32/100
0100
Medium · default modelHow is this calculated?
CVSS score
8.0/10
010
High · v3.1 (CVE.org)
EPSS score
0.56%
0%100%
Low · +0.08 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 0 · Related 2

Timeline

  1. 06-05-2025
    PublishedVulnerability first disclosed.
  2. 06-05-2025
    Last modifiedVulnerability information updated.

Description

vLLM is an inference and serving engine for large language models. In a multi-node vLLM deployment using the V0 engine, vLLM uses ZeroMQ for some multi-node communication purposes. The secondary vLLM hosts open a `SUB` ZeroMQ socket and connect to an `XPUB` socket on the primary vLLM host. When data is received on this `SUB` socket, it is deserialized with `pickle`. This is unsafe, as it can be abused to execute code on a remote machine. Since the vulnerability exists in a client that connects to the primary vLLM host, this vulnerability serves as an escalation point. If the primary vLLM host is compromised, this vulnerability could be used to compromise the rest of the hosts in the vLLM deployment. Attackers could also use other means to exploit the vulnerability without requiring access to the primary vLLM host. One example would be the use of ARP cache poisoning to redirect traffic to a malicious endpoint used to deliver a payload with arbitrary code to execute on the target machine. Note that this issue only affects the V0 engine, which has been off by default since v0.8.0. Further, the issue only applies to a deployment using tensor parallelism across multiple hosts, which we do not expect to be a common deployment pattern. Since V0 is has been off by default since v0.8.0 and the fix is fairly invasive, the maintainers of vLLM have decided not to fix this issue. Instead, the maintainers recommend that users ensure their environment is on a secure network in case this pattern is in use. The V1 engine is not affected by this issue.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.56%

Chance of exploitation in the next 30 days

Percentile

46%

Versus all other CVEs

30-day change

+0.08 pp

From 0.48% on 21-09-2026

21-09-202621-10-2026
EPSS score
0.56%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

PyPI1 product
  • vllm≥ 0.5.2, < 0.10.0
Vllm1 product
  • vllm≥ 0.5.2 (No fix recorded)
Vllm-project1 product
  • vllm≥ 0.5.2, ≤ 0.8.5.post1

3 vendors · 3 products

References

8 links