CVE-2025-30165 Remote Code Execution Vulnerability in vLLM Multi-Node Cluster Configuration

What is CVE-2025-30165?

CVE-2025-30165 is a high-severity unsafe deserialization vulnerability in Vllm Vllm, published on 6 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

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

Weakness: CWE-502

Which versions are affected by CVE-2025-30165?

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

Products include Vllm Vllm.

How do I fix CVE-2025-30165?

Upgrade vllm to 0.10.0 or later.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2025-30165 being exploited?

There is no known exploitation of CVE-2025-30165 in the wild and no public exploit code.

Other vulnerabilities in Vllm Vllm

• CVE-2025-32444 vLLM Vulnerable to Remote Code Execution via Mooncake Integration Critical 10.0
• CVE-2026-22778 vLLM leaks a heap address when PIL throws an error Critical 9.8
• CVE-2025-47277 vLLM Allows Remote Code Execution via PyNcclPipe Communication Service Critical 9.8
• CVE-2024-11041 Remote Code Execution in vllm-project/vllm Critical 9.8
• CVE-2026-48746 vLLM: OpenAI auth bypass Critical 9.1

All Vllm Vllm vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-9pcc-gvx5-r5wm, PYSEC-2026-2017.