vLLM is an inference and serving engine for large language models. Prior to 0.30.0, a caller can use the request-level media_io_kwargs field to select the GLMGA video backend and supply large values for the fps and max_frames options without a strict work ceiling. GLMGA constructs and deduplicates an attacker-sized pre-decode frame-index list, allowing a compact request and tiny valid video to consume disproportionate CPU time and memory in the shared media-loading executor. This issue is fixed in version 0.30.0.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/vllm-project/vllm/commit/8b6de0eb9a09ef53f20cf06bd4d17ee264b9c2a7 Patch
- https://github.com/vllm-project/vllm/pull/54935 Issue Tracking, Patch
- https://github.com/vllm-project/vllm/security/advisories/GHSA-58v5-2m8f-94pr Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.3 · vllmNVD modified 2026-10-16 20:39
Affected (CPE criteria) 1
cpe:2.3:a:vllm:vllm:*:*:*:*:*:*:*:*
References 4
- https://github.com/vllm-project/vllm/commit/8b6de0eb9a09ef53f20cf06bd4d17ee264b9c2a7 Patch
- https://github.com/vllm-project/vllm/pull/54935 Issue Tracking, Patch
- https://github.com/vllm-project/vllm/releases/tag/v0.30.0 Release Notes
- https://github.com/vllm-project/vllm/security/advisories/GHSA-58v5-2m8f-94pr Mitigation, Vendor Advisory