Summary
CVE-2026-116176 is a server-side request forgery (SSRF, CWE-918) vulnerability in vLLM versions 0.9.2 through 0.23.x. An API caller can supply a crafted X-Request-Id header that makes the P2pNcclConnector prefill worker open an outbound ZMQ connection to an attacker-controlled host. The CVE record lists a CVSS v4.0 score of 8.8 (High). It also lists a CVSS v3.1 score of 8.2 (High).
Technical details
- Root cause: Two defects combine.
OpenAIServing._base_request_idcopies the HTTPX-Request-Idheader verbatim without sanitization.P2pNcclConnector.parse_request_idthen extracts an arbitrary host:port from it with a permissive regex that has no validation or scheme checks. - Trigger conditions: The P2pNcclConnector is non-default. It must be explicitly enabled through
--kv-transfer-config(for example,"kv_connector":"P2pNcclConnector"with"kv_role":"kv_producer"). The attacker needs only a valid API key, or no key if authentication is disabled. - Attack vector: Network. The attacker sends an API request with an
X-Request-Idheader that embeds a malicious routing token. - Impact: The attacker can redirect the prefill worker’s connection to a host they control. The advisory says this can expose the NCCL communicator unique_id and KV-cache tensors, which include prompts and cached states. It can also disrupt worker availability by pointing the connection at an unresponsive host.
Affected software
- vLLM 0.9.2 through 0.23.x (before 0.24.0), only when P2pNcclConnector is enabled.
Severity
- CVSS v4.0: 8.8 (High) –
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N - CVSS v3.1: 8.2 (High) –
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
Mitigation and recommended actions
- Immediate: Upgrade to vLLM 0.24.0 or later. The fix removes the P2pNcclConnector entirely.
- If you can’t patch: The advisory documents no workaround. It advises not enabling P2pNcclConnector until you have upgraded. Limit access to the vLLM API to trusted clients, and restrict outbound network connections from prefill workers.

