CVE-2026-100652 vLLM 0.22.0 through 0.23.0 Denial of Service via stop_token_ids

High 8.2 Published Updated

Attackers can crash the vLLM engine by sending requests with invalid stop token IDs, requiring a service restart to recover.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-100652?

CVE-2026-100652 is a high-severity denial of service vulnerability in Vllm Vllm, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-20

Which versions are affected by CVE-2026-100652?

1 open source package ship an affected version, including vllm. It affects 1 product.

PackageAffectedFixed in
vllm PyPIFrom 0.22.00.24.0

Products include Vllm Vllm.

How do I fix CVE-2026-100652?

Upgrade vllm to 0.24.0 or later.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2026-100652 being exploited?

There is no known exploitation of CVE-2026-100652 in the wild and no public exploit code.

All Vllm Vllm vulnerabilities

Sources

Also known as GHSA-gxcm-7c4h-f56c, GHSA-qff2-492f-9fm4, MINI-7c86-3q7w-m4p7, MINI-7jrf-8pxp-f93g, PYSEC-2026-4185.

Is CVE-2026-100652 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free