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.
On October 6, 2026, a GitHub security advisory disclosed trust boundary flaws in vLLM's scale-out multimodal transport: the transport treats caller-provided features as trusted rendering results and does not bind-validate them against the current model's rendering contract. Five flaws allow authenticated requests to cause shared engine crashes, cross-request encoder cache poisoning or disclosure, and loss of transport integrity. The advisory marks affected versions as before 0.30.0 and the fixed version as 0.30.0. The report was submitted by Patch the Planet (a collaboration between Trail of Bits and OpenAI) and discovered using GPT-5.5-Cyber.