CVE-2026-100652CWE-20

CVE-2026-100652

Medium · published September 26, 2026

CVSS v3.1
5.9
EPSS
0%
Percentile
28.8
In the wild
Unconfirmed
What it is

vLLM versions 0.22.0 through 0.23.0 fail to validate stop_token_ids against vocabulary bounds in Rust HTTP and gRPC frontends, allowing out-of-vocabulary token IDs to reach MinTokensLogitsProcessor. Attackers can submit requests with min_tokens greater than zero and out-of-vocabulary stop_token_ids to trigger CUDA tensor indexing failures that leave EngineCore in a fatal state requiring service restart.

The record
Technical detail
CVSS v3.1
5.9 · MEDIUM
Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS v4.0
8.2 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
EPSS
0.00361 · 28.8th percentile
Weakness
CWE-20 · Improper Input Validation
Published
2026-09-26T18:16Z
Affected products (1)
ProductVersionsFixed in
vllm/vllm≥ 0.22.0, < 0.24.00.24.0
References (2)
https://github.com/vllm-project/vllm/security/advisories/GHSA-qff2-492f-9fm4 · [email protected]https://www.vulncheck.com/advisories/vllm-0.22.0-through-0.23.0-denial-of-service-via-stop-token-ids · [email protected]
EPSS history
Timeline
  • 28 SEP 03:25Z
    EPSS moved — → 0%
    epss
  • 26 SEP 13:23Z
    vLLM 0.22.0 through 0.23.0 Denial of Service via stop_token_ids
    cvelistv5