vLLM versions before 0.28.0 fail to validate the lower bound of token IDs in the /v1/embeddings and /pooling endpoints, allowing unauthenticated attackers to crash the engine by submitting negative token IDs. A single request with a negative token ID triggers a CUDA device-side assertion that poisons the GPU context, causing all subsequent requests to fail until the process restarts.
CVE-2026-93592
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-18. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (2)
Auto-updated Sep 18, 2026vLLM before 0.28.0 Denial of Service via negative token ID | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vllm-before-0.28.0-denial-of-service-via-negative-token-idDenial of service: a negative token id in `/v1/embeddings` or `/pooling` input kills the vLLM engine via a CUDA device-side assertion · Advisory · vllm-project/vllm · GitHub
https://github.com/vllm-project/vllm/security/advisories/GHSA-25q3-v2hm-8vpfVendor Advisories for CVE-2026-93592(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 16:12 UTCEG score recompute
- 2026-09-19 16:11 UTCGHSA enrichment
- 2026-09-19 05:20 UTCGHSA enrichment
- 2026-09-18 18:29 UTCEG score recompute
- 2026-09-18 18:29 UTCGHSA enrichment
- 2026-09-18 18:15 UTCEG score recompute
- 2026-09-18 18:14 UTCGHSA enrichment
- 2026-09-18 14:21 UTCEG score recompute
- 2026-09-18 13:29 UTCEG score recompute
- 2026-09-18 13:29 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-93592?
When was CVE-2026-93592 disclosed?
Is CVE-2026-93592 actively exploited?
What is the CVSS score of CVE-2026-93592?
How do I remediate CVE-2026-93592?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93592
Is Your Infrastructure Affected by CVE-2026-93592?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.