CVE-2026-116176
highvLLM from 0.9.2 before 0.24.0 contains a server-side request forgery vulnerability that allows API callers to force outbound connections by embedding a decode…
Vendor / product: Vllm — vllm
vLLM from 0.9.2 before 0.24.0 contains a server-side request forgery vulnerability that allows API callers to force outbound connections by embedding a decode address in the X-Request-Id header. Attackers can make a P2pNcclConnector prefill worker ZMQ-connect to an attacker host, leaking the NCCL unique_id and KV-cache tensors or blocking the worker.
CVSS
8.2
8.2 (CVSS v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L Severity source: NVD CVSS v3.1 (disclosure@vulncheck.com)
Timeline (UTC)
Published: 2026-10-25 14:16
Modified: 2026-10-28 15:41
NVD status: Analyzed
Last synced 15 hours ago
Verified against the source API 2026-10-28 16:01 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).
Affected products
vllm / vllm ≥0.9.2 <0.24.0
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
References
- https://github.com/vllm-project/vllm/security/advisories/GHSA-vfp2-c8pq-v6h6 disclosure@vulncheck.com
- https://www.vulncheck.com/advisories/vllm-0.9.2-before-0.24.0-ssrf-via-x-request-id-in-p2p... disclosure@vulncheck.com
Data sources
NVD CVE API 2.0 — fetched 2026-10-28 16:01 UTC · record ↗