cve.bz

CVE-2026-126399 vLLM 0.19.0 before 0.31.0 Resource Exhaustion via Request-Level num_frames

7.1 highEPSS 0.5%

High (7.1) in vllm-project vllm. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
vLLM from 0.19.0 before 0.31.0 contains a resource exhaustion vulnerability that allows inference clients to bypass the server frame limit by setting media_io_kwargs.video.num_frames in chat completion requests. Attackers can supply num_frames=-1 or a large value with many base64 JPEG frames, forcing VideoMediaIO to decode all frames and np.stack them, causing memory exhaustion.

Severity

CVSS 4.0

7.1 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% estimated probability of exploitation activity in the next 30 days; 42nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-126399 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126399?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126399?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126399 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126399

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126399](https://cve.bz/cve/badge/CVE-2026-126399.svg)](https://cve.bz/cve/CVE-2026-126399)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126399"><img src="https://cve.bz/cve/badge/CVE-2026-126399.svg" alt="CVE-2026-126399"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
vllm-project vllmfrom 0.19.0 before 0.31.0

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON