vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2026-116176

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

HIGH
8.2
CVSS Score
Published: October 25, 2026 at 01:20 PM UTC
Updated: October 28, 2026 at 03:41 PM UTC
1 product affected across 1 vendorvLLM

Using vllm by vllm-project?

Get instant alerts when new vulnerabilities affect vllm - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
HIGH8.2
Exploit prediction
EPSS 0.3%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

vLLM· Vllm
95%
0.9.2 ≤ v < 0.24.0
Vendor states this is fixed in 0.24.0 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (2)

Vendor Advisory
Source: cverecord
https://github.com/vllm-project/vllm/security/advisories/GHSA-vfp2-c8pq-v6h6
Third Party Advisory
Source: cverecord
https://www.vulncheck.com/advisories/vllm-0.9.2-before-0.24.0-ssrf-via-x-request-id-in-p2pncclconnector

CVSS

8.2HIGHVulnCheck
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusANALYZED
CWE
CWE-918

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card