vLLM is an inference and serving engine for large language models. From 0.24.0 until 0.30.0, the Qwen2VLVideoBackend and Qwen3VLVideoBackend classes accept request-level values for the media_io_kwargs.video.max_frames and media_io_kwargs.video.fps fields without enforcing server-side ceilings. An unauthenticated caller can submit these values to the /tokenize endpoint, causing the sampler to decode every frame selected from attacker-controlled video input, consume disproportionate frontend memory, and potentially terminate the API process before scheduling or admission control. The Rust frontend is not affected because it rejects the media_io_kwargs field. This issue is fixed in version 0.30.0.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/vllm-project/vllm/commit/ea723c81c3ea26425cb69503a5d5e90822a04a45 Patch
- https://github.com/vllm-project/vllm/pull/56729 Issue Tracking, Patch
- https://github.com/vllm-project/vllm/security/advisories/GHSA-x6mc-67gf-chw4 Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.3 · vllmNVD modified 2026-10-08 03:16
Affected (CPE criteria) 1
cpe:2.3:a:vllm:vllm:*:*:*:*:*:*:*:*
References 4
- https://github.com/vllm-project/vllm/commit/ea723c81c3ea26425cb69503a5d5e90822a04a45 Patch
- https://github.com/vllm-project/vllm/pull/56729 Issue Tracking, Patch
- https://github.com/vllm-project/vllm/releases/tag/v0.30.0 Release Notes
- https://github.com/vllm-project/vllm/security/advisories/GHSA-x6mc-67gf-chw4 Mitigation, Vendor Advisory