CVE-2026-100652vLLM 0.22.0 through 0.23.0 Denial of Service via stop_token_ids
Updated under an hour ago ()
Does this affect you?
It affects vllm-project vllm and 1 other product. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.36%, higher than 28% of scored CVEs.
Do this next
Free account, 1 product
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.
- CVSS
- 5.9 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- CWE-20
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.36% (percentile 28)
- Assigned by
- VulnCheck
- NVD analysis
- Analyzed
- Record last updated
- Sep 28, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
vllm-project vllm vllm_project:vllm (from the name) | from 0.22.0 before 0.24.0; 0.24.0 not affected | CNA record |
vllm vllm vllm:vllm | from 0.22.0 before 0.24.0 | NVD |
References
- https://github.com/vllm-project/vllm/security/advisories/GHSA-qff2-492f-9fm4vendor-advisory, exploit, mitigation
- https://www.vulncheck.com/advisories/vllm-0.22.0-through-0.23.0-denial-of-service-via-stop-token-idsthird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.