CVE-2026-93592

validatedZero produced an exploit or a check.

GHSA-25q3-v2hm-8vpf ↗EUVD-2026-82911 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−15dkevAttacks confirmed in the real world.
pip vllm < 0.28.0
fixed in 0.28.0
ETK-2026-1167Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/vllm
+22dTTV
46mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
public poc−15dtrigger signal (cve.org) +0dcheck available+22dagent stopped
−10d
0
+10d
+20d

description

vLLM versions before 0.28.0 accept negative token IDs through the token-ID input form of the embedding and pooling APIs. An unauthenticated remote client able to reach those endpoints can stop the serving engine, causing subsequent requests to fail until the process is restarted. Deployments are affected when untrusted callers can submit token-ID input to these endpoints.

mitigation

Upgrade vLLM to version 0.28.0 or later. Until upgraded, reject negative integer values in input at an API gateway, accept only string input from untrusted clients, and restrict access to the embedding and pooling endpoints.

fixed in 0.28.0

check
available
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.
deterministic
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.
0.54%44th percentile
agent run time
46m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-18 13:20Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
−15d
Δ to kevAttacks confirmed in the real world.
–

outcome

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-09-18 13:20Z
  2. 2026-09-18 13:20Z
  3. 2026-09-18 13:20Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1167",
  "cve_id": "CVE-2026-93592",
  "display_id": "CVE-2026-93592",
  "ghsa_id": "GHSA-25q3-v2hm-8vpf",
  "euvd_id": "EUVD-2026-82911",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated denial of service in vLLM embedding and pooling APIs",
  "summary": "vLLM versions before 0.28.0 accept negative token IDs through the token-ID input form of the embedding and pooling APIs. An unauthenticated remote client able to reach those endpoints can stop the serving engine, causing subsequent requests to fail until the process is restarted. Deployments are affected when untrusted callers can submit token-ID input to these endpoints.",
  "mitigation": "Upgrade vLLM to version 0.28.0 or later. Until upgraded, reject negative integer values in input at an API gateway, accept only string input from untrusted clients, and restrict access to the embedding and pooling endpoints.",
  "vendor": "pip",
  "product": "vllm",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 0.28.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "0.28.0"
      ],
      "package_name": "vllm",
      "purl": "pkg:pypi/vllm"
    }
  ],
  "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": 0.0054,
  "epss_percentile": 0.4461,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 45.80855565,
  "t0_at": "2026-09-18T13:20:05.365000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-10T14:47:29.617801+00:00",
      "days": 22.060697370381945,
      "is_lower_bound": false,
      "measured_at": "2026-09-18T13:20:05.365000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-09-03T18:08:31+00:00",
      "days": -14.799703298611112,
      "is_lower_bound": false,
      "measured_at": "2026-09-18T13:20:05.365000+00:00",
      "url": "https://github.com/vllm-project/vllm/security/advisories/GHSA-25q3-v2hm-8vpf"
    },
    "trigger_signal": {
      "at": "2026-09-18T13:20:05.365000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-18T13:20:05.365000+00:00",
      "url": "https://github.com/vllm-project/vllm/security/advisories/GHSA-25q3-v2hm-8vpf"
    }
  }
}

published 2026-10-10 14:01Z
last change 2026-10-21 11:52Z

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.