Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-93840: vLLM before 0.29.0 validates allowed_token_ids against tokenizer length instead of model output logits width i

22
Routine
LOW 3.7REMOTEUPGRADE

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

vLLM before 0.29.0 validates allowed_token_ids against tokenizer length instead of model output logits width in SamplingParams._validate_allowed_token_ids(). Attackers can supply token IDs above the output vocabulary that pass validation, causing LogitBiasState to corrupt GPU logits state and allow concurrent requests to sample tokens outside their allowlists.

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score3.7 (Low)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.2% (top 84%)
CISA exploited listNo
WeaknessCWE-129
Published2026-09-18
Last modified2026-09-28
Publisher (CNA): VulnCheck · Vendor: vllm

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

vllm vllm UPGRADE
Affected: < 0.29.0
Fixed in: 0.29.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy vllm || rpm -q vllm || vllm --version
2. UPGRADE to 0.29.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.
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-93840?

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

Is CVE-2026-93840 being exploited?

CVE-2026-93840 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-93840 affect?

CVE-2026-93840 affects vllm. Severity is low (CVSS 3.7). vLLM before 0.29.0 validates allowed_token_ids against tokenizer length instead of model output logits width in SamplingParams._validate_allowed_token_ids(). Attackers can supply token IDs above the output vocabulary that pass validation, c

How urgent is CVE-2026-93840?

Priority 22/100. 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.