Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Affected: vllm versions >=0.5.2 and <0.8.5, fixed in 0.8.5. In a multi-node deployment, the primary host binds a ZeroMQ XPUB socket to all interfaces, and any client with network access to that port can connect and receive internal vLLM state broadcast to secondary hosts. An attacker could also cause a denial of service by connecting many times without reading the published data. Upgrade to vllm 0.8.5. Before upgrading, keep the host off untrusted networks and block the socket's port from anything other than the other vLLM hosts.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0061, the 49th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:40 UTC First seen by agentprime
- 31 Oct 2026, 14:40 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-9f8f-2vmf-885j
- OSV: GHSA-9f8f-2vmf-885j
- github.com/vllm-project/vllm/security/advisories/GHSA-9f8f-2vmf-885j
- nvd.nist.gov/vuln/detail/CVE-2025-30202
- github.com/vllm-project/vllm/pull/17197
- github.com/vllm-project/vllm/pull/6183
- github.com/vllm-project/vllm/commit/a0304dc504c85f421d38ef47c64f83046a13641c
- github.com/advisories/GHSA-9f8f-2vmf-885j
- github.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2026-2016.yaml
- github.com/vllm-project/vllm
- pypi.org/project/vllm