CVE-2026-116176

waiting for further signalsZero needs more public information before it can validate it.

GHSA-3r8v-vh9c-f8hq ↗EUVD-2026-109437 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
vllm-project vllm >= 0.9.2, < 0.24.0
fixed in 0.24.0
CWE-918 Server-Side Request Forgery (SSRF)
ETK-2026-2599Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/vllm
4h 23msince last run
31mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h39m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

vLLM versions 0.9.2 through versions before 0.24.0 are affected by a server-side request forgery flaw. An attacker able to call the API and control the relevant request header may cause a worker to make outbound connections, potentially exposing worker data or disrupting the worker.

mitigation

Upgrade vLLM to version 0.24.0 or later. Until upgrades are complete, restrict API access to trusted callers and limit worker egress to approved destinations.

fixed in 0.24.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-25 13:20Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-25 13:20Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-116176

{
  "etk_id": "ETK-2026-2599",
  "cve_id": "CVE-2026-116176",
  "display_id": "CVE-2026-116176",
  "ghsa_id": "GHSA-3r8v-vh9c-f8hq",
  "euvd_id": "EUVD-2026-109437",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Server-side request forgery in vLLM",
  "summary": "vLLM versions 0.9.2 through versions before 0.24.0 are affected by a server-side request forgery flaw. An attacker able to call the API and control the relevant request header may cause a worker to make outbound connections, potentially exposing worker data or disrupting the worker.",
  "mitigation": "Upgrade vLLM to version 0.24.0 or later. Until upgrades are complete, restrict API access to trusted callers and limit worker egress to approved destinations.",
  "vendor": "vllm-project",
  "product": "vllm",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.9.2, < 0.24.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "0.24.0"
      ],
      "package_name": "vllm",
      "purl": "pkg:pypi/vllm"
    }
  ],
  "cwes": [
    918
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 31.25017965,
  "t0_at": "2026-10-25T13:20:16.476000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-25T13:20:16.476000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-25T13:20:16.476000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-116176"
    }
  }
}

published 2026-10-25 13:28Z
last change 2026-10-25 18:12Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.