Skip to main content

CVE-2026-93840: Improper Validation of Array Index in vllm-project vllm

0
Medium
Published: 09/18/2026 (09/18/2026, 21:32:27 UTC)
Source: CVE Database V5
Vendor/Project: vllm-project
Product: vllm

Description

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.

CVSS v4.0

Score 6.3medium

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vuln. Confidentiality
None
Vuln. Integrity
Low
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Affected software

vllm-project

vllm

Affected versions
>=0 <0.29.0
GitHub Actionsmore threats →ai
vllm-project/vllm
pkg:github/vllm-project/vllm
Affected versions
>=0 <0.29.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/18/2026, 19:47:38 UTC

Technical Analysis

The vulnerability in vllm prior to version 0.29.0 arises from validating allowed_token_ids against the tokenizer length rather than the model output logits width in the SamplingParams._validate_allowed_token_ids() function. This improper validation allows attackers to provide token IDs exceeding the output vocabulary size, which corrupts the LogitBiasState managing GPU logits. As a result, concurrent requests can sample tokens outside their intended allowlists, potentially bypassing token restrictions.

Potential Impact

Attackers can manipulate token sampling by supplying out-of-range token IDs, leading to corruption of GPU logits state and allowing concurrent requests to sample tokens outside their allowlists. This could undermine token-based restrictions in the model's output generation process. No known exploits in the wild have been reported.

Mitigation Recommendations

Upgrade to vllm version 0.29.0 or later, where this validation issue has been corrected. Patch status is confirmed by the affectedVersions field indicating versions before 0.29.0 are vulnerable. No vendor advisory content is provided, so check the official vllm-project resources for the official fix and further guidance.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-09-18T18:16:47.489Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6aad91cb55bf5e2cf5719191

Added to database: 09/18/2026, 19:32:27 UTC

Last enriched: 09/18/2026, 19:47:38 UTC

Last updated: 09/19/2026, 01:33:44 UTC

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses