CVE-2026-116176 vLLM 0.9.2 before 0.24.0 SSRF via X-Request-Id in P2pNcclConnector

What is CVE-2026-116176?

CVE-2026-116176 is a high-severity vulnerability in Vllm Vllm, published on 25 Oct 2026.

Official description

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.

Weakness: CWE-918

Which versions are affected by CVE-2026-116176?

1 open source package ship an affected version, including vllm. It affects 1 product.

Products include Vllm Vllm.

How do I fix CVE-2026-116176?

Upgrade vllm to 0.24.0 or later.

Is CVE-2026-116176 being exploited?

There is no known exploitation of CVE-2026-116176 in the wild and no public exploit code.

Other vulnerabilities in Vllm Vllm

• CVE-2025-32444 vLLM Vulnerable to Remote Code Execution via Mooncake Integration Critical 10.0
• CVE-2026-22778 vLLM leaks a heap address when PIL throws an error Critical 9.8
• CVE-2025-47277 vLLM Allows Remote Code Execution via PyNcclPipe Communication Service Critical 9.8
• CVE-2024-11041 Remote Code Execution in vllm-project/vllm Critical 9.8
• CVE-2026-48746 vLLM: OpenAI auth bypass Critical 9.1

All Vllm Vllm vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• GitHub advisory
• How this page is made

Also known as GHSA-3r8v-vh9c-f8hq, GHSA-vfp2-c8pq-v6h6, PYSEC-2026-4351.