CVE-2026-100652

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.
Configurations

Configuration 1 (hide)

cpe:2.3:a:vllm:vllm:*:*:*:*:*:*:*:*

History

06 Oct 2026, 19:22

Type Values Removed Values Added
First Time Vllm vllm
Vllm
References () https://github.com/vllm-project/vllm/security/advisories/GHSA-qff2-492f-9fm4 - () https://github.com/vllm-project/vllm/security/advisories/GHSA-qff2-492f-9fm4 - Exploit, Mitigation, Vendor Advisory
References () https://www.vulncheck.com/advisories/vllm-0.22.0-through-0.23.0-denial-of-service-via-stop-token-ids - () https://www.vulncheck.com/advisories/vllm-0.22.0-through-0.23.0-denial-of-service-via-stop-token-ids - Third Party Advisory
CPE cpe:2.3:a:vllm:vllm:*:*:*:*:*:*:*:*

26 Sep 2026, 14:16

Type Values Removed Values Added
New CVE

Information

Published : 2026-09-26 14:16

Updated : 2026-10-06 19:22


NVD link : CVE-2026-100652

Mitre link : CVE-2026-100652

CVE.ORG link : CVE-2026-100652


JSON object : View

Products Affected

vllm

  • vllm
CWE
CWE-20

Improper Input Validation