gcdRadar
archive/Patch now/AIR-2026-1504
closedclosed 25 Oct 2026Patch now2 Disclosed vulnerabilityAI

CVE-2026-116176: vLLM server-side request forgery leads to NCCL unique_id and KV-cache leakage

vLLM

A server-side request forgery vulnerability in vLLM allows API callers to force outbound connections using a crafted X-Request-Id header. Attackers can leak sensitive cache tensors or block prefill workers.

disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why

CVSS
8.8
EPSS
<0.01 · top 75% · 2026-11-13
fix status
Fix status unknown
first report
25 Oct 2026
last update
25 Oct 2026

Timeline · 1

  1. 25 Oct 2026CVE-2026-116176: vLLM from 0.9.2 before 0.24.0 contains a server-side request forgery vulnerability that allows API callers to force outbound…

Sources · 1

Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.

Classification

AI role
Attack on AI
categories
Infrastructure vulnerabilityData leak
severity
2 · Disclosed vulnerability
fix status
Fix status unknown
targets
Framework / tooling
mitre atlas
no technique for these categories
dates
happened 25 Oct 2026 · first reported 25 Oct 2026
origin
NVD
Vulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
record
confidence 0.95 · created 2026-10-25 16:18Z · updated 2026-10-25 16:18Z

Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned

Copy a brief

This record as a short Markdown brief, for a ticket, a chat or a coding agent.

the brief as text
# CVE-2026-116176: vLLM server-side request forgery leads to NCCL unique_id and KV-cache leakage

https://gcdradar.vercel.app/incidents/cve-2026-116176-vllm-server-side-request-forgery-leads-to-nc · AIR-2026-1504 · closed 2026-10-25

- Lane: Patch now
- Severity: 2 (Disclosed vulnerability)
- Fix status: Fix status unknown
- First reported: 2026-10-25
- AI role: Attack on AI
- Products: vLLM
- CVE ids: CVE-2026-116176
- CVSS: 8.8

## Summary

A server-side request forgery vulnerability in vLLM allows API callers to force outbound connections using a crafted X-Request-Id header. Attackers can leak sensitive cache tensors or block prefill workers.

## What to do

No action recorded; read the sources below and the vendor's advisory.

## Latest updates

- 2026-10-25: CVE-2026-116176: vLLM from 0.9.2 before 0.24.0 contains a server-side request forgery vulnerability that allows API callers to force outbound… (https://nvd.nist.gov/vuln/detail/CVE-2026-116176)

## Sources

- 2026-10-25 NVD: CVE-2026-116176: vLLM from 0.9.2 before 0.24.0 contains a server-side request forgery vulnerability that allows API callers to force outbound… https://nvd.nist.gov/vuln/detail/CVE-2026-116176

Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.

Related

  1. closed7.1
    vLLM CVE-2026-114054: vLLM cache aliasing vulnerability exposes processed media and KV state

    Patch now · Disclosed · since 21 Oct 2026 · CVE-2026-114054

    AI
  2. closed5.3
    vLLM CVE-2026-73558: vLLM data leakage vulnerability in activation kernels

    Patch now · Disclosed · since 13 Aug 2026 · updated 8 Sep 2026 · CVE-2026-73558

    AI
  3. closed5.3
    vLLM CVE-2026-73555: Information disclosure vulnerability in vLLM request validation handling

    Patch now · Disclosed · since 13 Aug 2026 · updated 4 Sep 2026 · CVE-2026-73555

    AI
  4. closed7.5
    vLLM CVE-2025-30202: Data Exposure via ZeroMQ in Multi-Node vLLM Deployment

    Patch now · Disclosed · since 29 Apr 2025 · updated 30 Apr 2025 · CVE-2025-30202

    AI
  5. closed
    AI
  6. live
    SGLang SGLang RCE Exploit Breaches NEAR AI, Steals Data From 18 Agents

    Breaches & attacks · Exploited · since 8 Nov 2026

    AI