CVE-2026-93840: Improper Validation of Array Index in vllm-project vllm
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.
AI Analysis
Technical Summary
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.
CVE-2026-93840: Improper Validation of Array Index in vllm-project 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
Affected software
vllm-project
vllm
pkg:github/vllm-project/vllmRun 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
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.
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 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.