vLLM Qwen video sampler max_frames has no upper limit, leading to memory exhaustion DoS
Start here
A GitHub security advisory states that vLLM's Qwen2-VL and Qwen3-VL video samplers do not enforce the existing num_frames upper limit on request-level max_frames, which may lead to memory exhaustion. In the advisory's CPU-only test, the number of decoded frames increased from 60 to 900, and peak RSS increased from 2,271 MiB to 13,629 MiB; these values correspond only to that test. Paths such as /tokenize do not require vLLM API-key authentication; the Rust frontend is not affected because it rejects the relevant media options.
Generated by AI from reports · Updated 2 days ago
Progress timeline
- GitHub 安全公告SelectedvLLM's Qwen2-VL/Qwen3-VL video sampler does not enforce the request-level max_frames limit, which can lead to unauthenticated memory exhaustion
vLLM's Qwen2-VL and Qwen3-VL video samplers do not enforce the existing num_frames cap on request-level max_frames, which can lead to memory exhaustion. In the advisory's CPU-only test, decoded frames increased from 60 to 900 and peak RSS increased from 2,271 MiB to 13,629 MiB; these values correspond only to that test. Paths such as /tokenize do not require vLLM API-key authentication; the Rust frontend is unaffected because it rejects the relevant media options. The GitHub advisory marks affected versions as >= 0.24.0, < 0.30.0 and the fixed version as 0.30.0.
Related discussion
Attention trend
New sources per day
- Oct 6New1 sources (1 outlets,0 accounts)
- Oct 7New0 sources (0 outlets,0 accounts)
- Oct 8New0 sources (0 outlets,0 accounts)
- Oct 9New0 sources (0 outlets,0 accounts)
- Oct 10New0 sources (0 outlets,0 accounts)
- Oct 11New0 sources (0 outlets,0 accounts)
- Oct 12New0 sources (0 outlets,0 accounts)
- Oct 13New0 sources (0 outlets,0 accounts)