CVE-2026-105758
vLLM is an inference and serving engine for large language models. …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/vllm-project/vllm/commit/ea723c81c3ea26425cb69503a5d5e90822a04a45
- github.com/vllm-project/vllm/pull/56729
- github.com/vllm-project/vllm/releases/tag/v0.30.0
- github.com/vllm-project/vllm/security/advisories/GHSA-x6mc-67gf-chw4
- github.com/advisories/GHSA-x6mc-67gf-chw4
- nvd.nist.gov/vuln/detail/CVE-2026-105758
- cve.org/CVERecord?id=CVE-2026-105758
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.