CVE-2026-116179

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

GHSA-6vc9-vh4h-cxh4 ↗EUVD-2026-109440 ↗

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.18.0, < 0.31.0
fixed in 0.31.0
ETK-2026-2604Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 52msince last run
39mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+6h02m
0
+2h
+4h
+8h
+10h
+12h

description

vLLM versions 0.18.0 through 0.30.x can consume excessive memory while processing inline video or JPEG media. An API client may crash the frontend by bypassing the configured frame limit through media I/O request options. Exposure requires an API endpoint that accepts affected media inputs from the attacker.

mitigation

Upgrade vLLM to version 0.31.0 or later. Until upgraded, restrict untrusted access to media-processing API endpoints and limit or reject inline media requests where feasible.

fixed in 0.31.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.
–
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
39m
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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2604",
  "cve_id": "CVE-2026-116179",
  "display_id": "CVE-2026-116179",
  "ghsa_id": "GHSA-6vc9-vh4h-cxh4",
  "euvd_id": "EUVD-2026-109440",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Resource exhaustion in vLLM media frame processing",
  "summary": "vLLM versions 0.18.0 through 0.30.x can consume excessive memory while processing inline video or JPEG media. An API client may crash the frontend by bypassing the configured frame limit through media I/O request options. Exposure requires an API endpoint that accepts affected media inputs from the attacker.",
  "mitigation": "Upgrade vLLM to version 0.31.0 or later. Until upgraded, restrict untrusted access to media-processing API endpoints and limit or reject inline media requests where feasible.",
  "vendor": "vllm-project",
  "product": "vllm",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.18.0, < 0.31.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.31.0"
      ],
      "package_name": "vllm",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 38.91047328333333,
  "t0_at": "2026-10-25T13:20:18.520000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-25T13:20:18.520000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-25T13:20:18.520000+00:00",
      "url": "https://github.com/advisories/GHSA-6vc9-vh4h-cxh4"
    }
  }
}

published 2026-10-25 16:34Z
last change 2026-10-25 21:01Z

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.