vLLM OpenCVDynamicOpenPanguVideoBackend: request-level num_frames without a ceiling — unauthenticated memory/CPU exhaustion (OOM-kill) on an
GHSA-894j-wg8m-63h8 · published 2026-10-27
- Severity
- Medium
- CVSS score
- 5.3
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 0.31.0
OpenCVDynamicOpenPanguVideoBackend (vllm/multimodal/video.py:1222-1260) drives its frame-index computation from the request-controlled num_frames with no ceiling. The backend is registered without a video_processor binding, so no model selects it by default — but VideoMediaIO honors request-level media_io_kwargs.video.video_backend for any registered CPU loader (merge_kwargs, vllm/multimodal/media/video.py:42-90, strips only hw_decoders/pool_size/device/unconfigured-GPU backends and clamps none of the sampling knobs). …
Upgrade vllm to 0.31.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Backend: clamp num_frames before np.linspace (e.g. min(num_frames, total_frames_num) or a class-level cap) and treat fps=-1 the same. Central: land the num_frames clamp in VideoMediaIO.merge_kwargs (where PR #51969 is adding it) so per-backend audits stop missing siblings, and consider gating request-level video_backend selection to an allowlist.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| vllm | PyPI | >= 0.30.0, < 0.31.0 | 0.31.0 |
- HightsParticles: Unbounded HTTP Request Body Buffering in @tsparticles/mcp-server Leads to Remote DoS@tsparticles/mcp-server
- HighMCP TypeScript SDK: HTTP server transports and handlers did not limit request body size or JSON-RPC batch length@modelcontextprotocol/hono, @modelcontextprotocol/node, @modelcontextprotocol/sdk, @modelcontextprotocol/server
- HighMCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation@modelcontextprotocol/sdk, @modelcontextprotocol/server
- HighHTTP server transports and OAuth endpoints read request bodies with no size limitmcp, mcp
- HighLMDeploy vulnerable to arbitrary code execution via eval() of untrusted quant_dtype in model config loadinglmdeploy
- HighRMCP: Unauthenticated permanent session-table leak in rmcp Streamable HTTP server transport leads to remote denial-of-servicermcp
- CriticalvLLM: OpenAI auth bypassvllm
- CriticalvLLM has RCE In Video Processingvllm
- CriticalvLLM Allows Remote Code Execution via PyNcclPipe Communication Servicevllm
- CriticalvLLM Vulnerable to Remote Code Execution via Mooncake Integrationvllm
- CriticalCVE-2025-24357 Malicious model remote code execution fix bypass with PyTorch < 2.6.0vllm
- CriticalvLLM Deserialization of Untrusted Data vulnerabilityvllm
The impact, patch and workaround text comes from the advisory, shortened (published by vLLM). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.