GPU VulnDB

Database/AI/ML frameworks & serving

vLLM: unchecked min_pixels in MiniMax M3 VL video processing exhausts host CPU and memory

CVSS 6.9CVE-2026-126396AI/ML frameworks & servingcurated

Impact

The MiniMax M3 VL video processor accepts min_pixels from the request (via mm_processor_kwargs) without checking its range or that it is no larger than max_pixels. The video-wide pixel budget only applies when max_long_side_pixel is set, and that defaults to None. A client can therefore inflate every decoded frame and use up host CPU and RAM. Frame decoding happens on the host, so one request can starve or crash the worker serving every other tenant on that replica. Only deployments serving the MiniMax M3 VL model are affected.

Who can reach it

Any API client that can send video requests to a vLLM instance serving MiniMax M3 VL. Authentication is whatever the deployment enforces, and the record states none is needed.

What to do

Upgrade vLLM to 0.31.0 or later, which affects 0.24.0 through 0.30.x, and restart each serving replica. Until then, set max_long_side_pixel to enforce the video pixel budget, or strip mm_processor_kwargs from untrusted requests at the gateway.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.