Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

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

40
This week
MEDIUM 5.9REMOTEUPGRADE

CVE-2026-100652 is a medium-severity flaw (CVSS 5.9) affecting vllm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.9 (Medium)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.4% (top 64%)
CISA exploited listNo
WeaknessCWE-20
Published2026-09-26
Last modified2026-10-06
Publisher (CNA): VulnCheck · Vendor: vllm

Share: LinkedIn · X · Reddit

Last updated 2026-10-06 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vllm vllm UPGRADE
Affected: >= 0.22.0 and < 0.24.0
Fixed in: 0.24.0
Safe to downgrade to: a release before 0.22.0
1. Check installed version
apt-cache policy vllm || rpm -q vllm || vllm --version
2. UPGRADE to 0.24.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade vllm
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade vllm
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.22.0 (Debian / Ubuntu)
apt-cache madison vllm sudo apt install vllm=<VERSION_BEFORE_0.22.0> sudo apt-mark hold vllm
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list vllm sudo dnf downgrade vllm-<VERSION_BEFORE_0.22.0> sudo dnf versionlock add vllm
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-100652?

vllm: upgrade to 0.24.0. Exact commands for each OS are on this page.

Is CVE-2026-100652 being exploited?

CVE-2026-100652 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-100652 affect?

CVE-2026-100652 affects vllm. Severity is medium (CVSS 5.9). 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_to

How urgent is CVE-2026-100652?

Priority 40/100. Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.