vLLM before 0.28.0 Denial of Service via negative token ID (CVE-2026-93592) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-93592

vLLM before 0.28.0 Denial of Service via negative token ID

Answer in brief

CVE-2026-93592 records a Unknown severity vulnerability in vLLM before 0.28.0 Denial of Service via negative token ID. The current sources do not mark it as known exploited. The current feed maps vllm-project/vllm (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 18, 2026Updated Sep 18, 2026Source checked Sep 18, 2026First seen by HOL Sep 18, 2026Material review Sep 18, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps vllm-project/vllm (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
vllm-project/vllmgeneric	>=0 <0.28.0	0.28.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for vllm-project/vllm.
Review the reported fix. Update vllm-project/vllm to 0.28.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 18, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.