CVE-2026-44222: CWE-129: Improper Validation of Array Index in vllm-project vllm
vLLM is an inference and serving engine for large language models (LLMs). From 0.6.1 to before 0.20.0, there is a a Token Injection vulnerability in vLLM’s multimodal processing. Unauthenticated, text-only prompts that spell special tokens are interpreted as control. Image and video placeholder sequences supplied without matching data cause vLLM to index into empty grids during input-position computation, raising an unhandled IndexError and terminating the worker or degrading availability. Multimodal paths that rely on image_grid_thw/video_grid_thw are affected. This vulnerability is fixed in 0.20.0.
AI Analysis
Technical Summary
vLLM, an inference and serving engine for large language models, has a Token Injection vulnerability in its multimodal processing component in versions >= 0.6.1 and < 0.20.0. When unauthenticated text-only prompts include special tokens interpreted as control, and when image/video placeholder sequences lack corresponding data, the software attempts to index into empty grids during input-position computation. This improper validation of array indices (CWE-129) leads to an unhandled IndexError, causing worker termination or availability degradation. The vulnerability affects multimodal paths that use image_grid_thw or video_grid_thw. The issue is resolved in vLLM 0.20.0.
Potential Impact
The vulnerability can cause denial of service by terminating worker processes or degrading availability of the vLLM service when malformed multimodal inputs are processed. There is no impact on confidentiality or integrity reported. No known exploits in the wild have been identified.
Mitigation Recommendations
Upgrade vLLM to version 0.20.0 or later, where this vulnerability is fixed. Since the vendor advisory indicates the issue is resolved in 0.20.0, applying this official fix is the recommended remediation. No other mitigation steps are specified.
CVE-2026-44222: CWE-129: Improper Validation of Array Index in vllm-project vllm
Description
vLLM is an inference and serving engine for large language models (LLMs). From 0.6.1 to before 0.20.0, there is a a Token Injection vulnerability in vLLM’s multimodal processing. Unauthenticated, text-only prompts that spell special tokens are interpreted as control. Image and video placeholder sequences supplied without matching data cause vLLM to index into empty grids during input-position computation, raising an unhandled IndexError and terminating the worker or degrading availability. Multimodal paths that rely on image_grid_thw/video_grid_thw are affected. This vulnerability is fixed in 0.20.0.
CVSS v3.1
Score 6.5medium
Affected software
pkg:github/vllm-project/vllmRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
vLLM, an inference and serving engine for large language models, has a Token Injection vulnerability in its multimodal processing component in versions >= 0.6.1 and < 0.20.0. When unauthenticated text-only prompts include special tokens interpreted as control, and when image/video placeholder sequences lack corresponding data, the software attempts to index into empty grids during input-position computation. This improper validation of array indices (CWE-129) leads to an unhandled IndexError, causing worker termination or availability degradation. The vulnerability affects multimodal paths that use image_grid_thw or video_grid_thw. The issue is resolved in vLLM 0.20.0.
Potential Impact
The vulnerability can cause denial of service by terminating worker processes or degrading availability of the vLLM service when malformed multimodal inputs are processed. There is no impact on confidentiality or integrity reported. No known exploits in the wild have been identified.
Mitigation Recommendations
Upgrade vLLM to version 0.20.0 or later, where this vulnerability is fixed. Since the vendor advisory indicates the issue is resolved in 0.20.0, applying this official fix is the recommended remediation. No other mitigation steps are specified.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-05T15:42:40.518Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a038bd7cbff5d8610164964
Added to database: 05/12/2026, 20:21:43 UTC
Last enriched: 05/12/2026, 20:39:11 UTC
Last updated: 06/26/2026, 20:56:20 UTC
Views: 90
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.