CVE-2026-126399
A client could override a vLLM server’s video frame limit
vLLM · Video media loading
First documented disclosure · Review checkpoint
Summary
Request-level settings could replace the frame limit chosen by the operator. Decoding more frames than the deployment allowed could exhaust worker memory.
Severity and exploitation evidence
High · 7.1/10 · CVSS 4.0. Severity source.
Exploitation not established: The reviewed sources describe the weakness and correction. They identify no confirmed malicious use.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
Request-level settings could replace the frame limit chosen by the operator.
Conditions required
An inference client can submit video to an affected deployment that accepts request-level media settings.
Potential impact
Decoding more frames than the deployment allowed could exhaust worker memory.
Affected versions and configurations
0.19.0 through releases before 0.31.0.
Fix and mitigation status
0.31.0 for this issue.
Practical next steps
Use a supported vLLM release containing the 0.31.0 fix. Keep client-controlled multimodal settings disabled for untrusted users.
Operating lesson
Verify that per-request settings can lower an operator limit without raising or removing it.
Evidence and limits
The original frame-loader check in 0.19.0 did not cover the later request override. The issuing CNA published the CVE record on 2026-11-13.
Sources
- vLLM project security advisory
Primary source ·
- Public vLLM project change
Primary source ·
- Issuing CNA record and severity assessment
Primary source ·