logo_clicknbuy.png

CVE-2025-30202 – vLLM ZeroMQ Denial of Service and Data Exposure Vulnerability

The following table lists the changes that have been made to the
CVE-2025-30202 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution
of a vulnerability, and for identifying the most recent changes that may
impact the vulnerability’s severity, exploitability, or other characteristics.

  • New CVE Received
    by [email protected]

    Apr. 30, 2025

    Action Type Old Value New Value
    Added 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.
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
    Added CWE CWE-770
    Added Reference https://github.com/vllm-project/vllm/commit/a0304dc504c85f421d38ef47c64f83046a13641c
    Added Reference https://github.com/vllm-project/vllm/pull/6183
    Added Reference https://github.com/vllm-project/vllm/security/advisories/GHSA-9f8f-2vmf-885j
Share the Post:

Related Posts