CVE-2026-116176EUVD-2026-109437GHSA-3R8V-VH9C-F8HQGHSA-VFP2-C8PQ-V6H6PYSEC-2026-4351
vLLM 0.9.2 before 0.24.0 SSRF via X-Request-Id in P2pNcclConnector
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.24.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- vllm-project vllm
From 0.9.2 · fixed in 0.24.0
- vllmPyPI
From 0.9.2 · fixed in 0.24.0