mediumCVSS 5.9NVD status: Analyzed

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.

ComponentvLLM
Severitymedium (CVSS 5.9)
CVSS vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Published (NVD)2026-09-26
Last modified2026-10-06
Affected versions
vllm >= 0.22.0, < 0.24.0
Fixed in0.24.0
WeaknessCWE-20
CISA KEVnot listed

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

Does CVE-2026-100652 hit the version you run?Paste your docker-compose.yml, requirements.txt or package.json. The scanner checks your pinned versions against this CVE and every other one we track for vLLM.
Check my stack

What to do

  • Upgrade vLLM to 0.24.0 or later.
  • Do not expose the component's API or UI to the internet without authentication in front of it.

Sources

Read more

Other vLLM CVEs

All vLLM CVEs