Duplicate Advisory: vllm p2p never connected zmq_exhaustion

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

• CISA KEV Not listed.
• EPSS No score.

Timeline

1. 31 Oct 2026, 14:07 UTC First seen by agentprime
2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-8qpc-6rxx-4pxf
• OSV: GHSA-8qpc-6rxx-4pxf
• nvd.nist.gov/vuln/detail/CVE-2026-94624
• github.com/vllm-project/vllm/pull/51504
• github.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2026-4006.yaml
• github.com/vllm-project/vllm
• github.com/vllm-project/vllm/blob/v0.29.0/vllm/v1/kv_offload/tiering/p2p/control/zmq.py#L240-L260
• github.com/vllm-project/vllm/blob/v0.29.0/vllm/v1/kv_offload/tiering/p2p/manager.py#L667-L677
• www.vulncheck.com/advisories/vllm-through-0.29.0-denial-of-service-via-unbounded-p2p-kv-offloading-sessions

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.