---
id: "CVE-2026-126396"
page: "https://infrastack.ai/live/CVE-2026-126396"
kind: "vulnerability"
aliases: ["CVE-2026-126396"]
title: "vLLM: unchecked request pixel setting lets clients exhaust CPU and memory"
severity: "medium"
cvss: 6.9
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-inference", "ai-tooling", "minimax-m3-vl", "self-hosted", "vllm"]
not_affected_if: ["no-minimax-m3-vl", "no-video-input", "outside-version-range"]
published_at: "2026-11-13T10:17:43+00:00"
first_seen_at: "2026-11-13T10:47:19+00:00"
updated_at: "2026-11-13T10:54:45+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-126396", "first_seen_at": "2026-11-13T10:47:19+00:00"}]
exploit_sources: []
---

# vLLM: unchecked request pixel setting lets clients exhaust CPU and memory

Link for people: https://infrastack.ai/live/CVE-2026-126396 (this .md is for agents)

vLLM's MiniMax M3 VL video processor accepts a request-level min_pixels value without validation, so a client can enlarge every decoded frame. This drives excessive CPU and host-memory use that can disrupt workers or the service.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed vLLM version with `pip show vllm` and compare it to the fixed range.
- Look for MiniMax M3 VL model deployments that accept `mm_processor_kwargs` from API clients.
- Check whether `max_long_side_pixel` is set in the video processor configuration; it defaults to None.

## Fix

- vLLM: move to `0.31.0` or later.

## Timeline

- 2026-11-13T10:47:19+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-126396

## Documents

- [advisory] Maintainer's advisory: github.com https://github.com/vllm-project/vllm/security/advisories/GHSA-w4cg-mhc7-mgw3
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/vllm-from-0.24.0-before-0.31.0-resource-exhaustion-via-minimax-m3-min-pixels

## From the sources

vLLM from 0.24.0 before 0.31.0 contains a resource exhaustion vulnerability in the MiniMax M3 VL video processor, which accepts request-level min_pixels without range or min_pixels <= max_pixels validation. Its video-wide pixel budget is enforced only when max_long_side_pixel is set, and that value defaults to None. API clients can supply a large min_pixels via mm_processor_kwargs to enlarge every decoded frame, causing excessive CPU and host-memory consumption that may disrupt workers or the service.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_