| Component | vLLM |
| Severity | high (CVSS 7.5) |
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| Published (NVD) | 2026-10-25 |
| Affected versions | >= 0.18.0, < 0.31.0 from the CVE Program record written by the CNA that assigned the CVE |
| Fixed in | 0.31.0 |
| Weakness | CWE-770 |
| CISA KEV | not listed |
NVD description
vLLM from 0.18.0 before 0.31.0 contains a resource exhaustion vulnerability that allows API clients to bypass the video/jpeg frame-count cap by overriding num_frames through media_io_kwargs. Attackers can set num_frames to -1 with a large inline video so VideoMediaIO.load_base64 decodes every frame, exhausting memory and crashing the API frontend.
What to do
- Upgrade vLLM to
0.31.0or later. - Do not expose the component's API or UI to the internet without authentication in front of it.
Sources
- NVD: CVE-2026-116179
- https://github.com/vllm-project/vllm/security/advisories/GHSA-4m6g-h9mv-wqjc
- https://www.vulncheck.com/advisories/vllm-0.18.0-before-0.31.0-memory-exhaustion-via-media-io-kwargs-num-frames-override