Resource exhaustion in Vllm-Project Vllm
CVE-2026-116179
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.
Published .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- github.com/vllm-project/vllm/security/advisories/GHSA-4m6g-h9mv-wqjc (vendor-advisory)
- www.vulncheck.com/advisories/vllm-0.18.0-before-0.31.0-memory-exhaustion-via-me… (third-party-advisory)
Frequently asked questions
- What is CVE-2026-116179?
- CVE-2026-116179 is a high-severity vulnerability in Vllm-Project Vllm, classified under Allocation of Resources Without Limits or Throttling. CVSS score: 7.5/10. Published 2026-10-25.
- How severe is CVE-2026-116179?
- High severity. CVSS v3 base score is 7.5 out of 10.