| Component | vLLM |
| Severity | high (CVSS 8.2) |
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L |
| Published (NVD) | 2026-10-25 |
| Affected versions | >= 0.9.2, < 0.24.0 from the CVE Program record written by the CNA that assigned the CVE |
| Fixed in | 0.24.0 |
| Weakness | CWE-918 |
| CISA KEV | not listed |
NVD 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.
What to do
- Upgrade vLLM to
0.24.0or later. - Do not expose the component's API or UI to the internet without authentication in front of it.
Sources
- NVD: CVE-2026-116176
- https://github.com/vllm-project/vllm/security/advisories/GHSA-vfp2-c8pq-v6h6
- https://www.vulncheck.com/advisories/vllm-0.9.2-before-0.24.0-ssrf-via-x-request-id-in-p2pncclconnector