CVE-2026-116179

vLLM 0.18.0 before 0.31.0 Memory Exhaustion via media_io_kwargs num_frames Override

Published Oct 25, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

vLLM versions 0.18.0 through 0.30.x contain a resource exhaustion flaw caused by the ability of API clients to override the num_frames parameter through media_io_kwargs. By setting num_frames to –1 and supplying a large inline video, VideoMediaIO.load_base64 processes every frame, consuming excessive memory and causing the API to crash. The flaw is a classic example of a Denial of Resource condition, classified as CWE-770, and results in a denial of service that can affect availability for any user of the impacted API endpoint.

Affected Systems

The vulnerability affects the vLLM project’s vLLM library. All releases from 0.18.0 up to and including 0.30.x are impacted; the issue is resolved in 0.31.0 and newer releases. Affected vendors include the vllm-project.

Risk and Exploitability

The base CVSS score is 8.7, indicating a high severity. EPSS data is not available, and the vulnerability is not listed in the CISA KEV catalog. Attackers can exploit the flaw by sending crafted requests to the vLLM API, where the overridden num_frames causes the server to drain memory. The attack vector is therefore an API client with the ability to control media_io_kwargs payloads, typically over a network connection. Because it does not require elevated privileges or prior authentication, the vulnerability can lead to a service outage for the exposed endpoint.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to vLLM 0.31.0 or later to eliminate the memory‑exhaustion flaw.
  • If an upgrade is not immediately possible, enforce strict limits on media_io_kwargs, disallow negative or excessively large num_frames values, and implement request size or frame‑count checks on the API side.
  • Apply application‑level memory or resource quotas and monitor memory usage to detect and mitigate potential exhaustion attempts.

Generated by OpenCVE AI on October 25, 2026 at 16:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Vllm-project
Vllm-project vllm
Vendors & Products Vllm-project
Vllm-project vllm
Type Values Removed Values Added
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.
Title vLLM 0.18.0 before 0.31.0 Memory Exhaustion via media_io_kwargs num_frames Override
First Time appeared Vllm
Vllm vllm
Weaknesses CWE-770
CPEs cpe:2.3:a:vllm:vllm:*:*:*:*:*:*:*:*
Vendors & Products Vllm
Vllm vllm
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

cvssV4_0

{'score': 8.7, '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'}

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 26, 2026, 4:43 PM
Reserved
Oct 25, 2026, 12:26 PM
Status
Analyzed
Published
Oct 25, 2026, 2:16 PM
Modified
Oct 28, 2026, 3:40 PM
Severity
Important
Public date
Oct 25, 2026, 1:20 PM