highCVSS 7.5NVD status: Analyzed

CVE-2025-30202

vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs.

ComponentvLLM
Severityhigh (CVSS 7.5)
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published (NVD)2025-04-30
Last modified2026-06-17
Affected versions
vllm >= 0.5.2, < 0.8.5
Fixed in0.8.5
WeaknessCWE-770
CISA KEVnot listed

NVD description

vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. Versions starting from 0.5.2 and prior to 0.8.5 are vulnerable to denial of service and data exposure via ZeroMQ on multi-node vLLM deployment. In a multi-node vLLM deployment, vLLM uses ZeroMQ for some multi-node communication purposes. The primary vLLM host opens an XPUB ZeroMQ socket and binds it to ALL interfaces. While the socket is always opened for a multi-node deployment, it is only used when doing tensor parallelism across multiple hosts. Any client with network access to this host can connect to this XPUB socket unless its port is blocked by a firewall. Once connected, these arbitrary clients will receive all of the same data broadcasted to all of the secondary vLLM hosts. This data is internal vLLM state information that is not useful to an attacker. By potentially connecting to this socket many times and not reading data published to them, an attacker can also cause a denial of service by slowing down or potentially blocking the publisher. This issue has been patched in version 0.8.5.

Does CVE-2025-30202 hit the version you run?Paste your docker-compose.yml, requirements.txt or package.json. The scanner checks your pinned versions against this CVE and every other one we track for vLLM.
Check my stack

What to do

  • Upgrade vLLM to 0.8.5 or later.
  • Do not expose the component's API or UI to the internet without authentication in front of it.

Sources

Read more

Other vLLM CVEs

All vLLM CVEs