CVE-2026-105758

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.

CVSS 3.1

5.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS

0.3% chance of exploitation in the next 30 days; higher than 22% of CVEs (scores of 2026-10-25)

CWE

CWE-770

Published

2026-10-05

Modified

2026-10-08

Record from

the NVD, synced 2026-10-19

Affected

• vllm:vllm

Packages (OSV)

References

• https://github.com/vllm-project/vllm/commit/ea723c81c3ea26425cb69503a5d5e90822a04a45
• https://github.com/vllm-project/vllm/pull/56729
• https://github.com/vllm-project/vllm/releases/tag/v0.30.0
• https://github.com/vllm-project/vllm/security/advisories/GHSA-x6mc-67gf-chw4

Check your stackJSON