Read the docs

Resource exhaustion in vLLM OpenPangu video backend via num_frames

Priority LOW 30CWE-770Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · Low
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-770.

Summary

vLLM from 0.30.0 before 0.31.0 contains a resource exhaustion flaw in the OpenCVDynamicOpenPanguVideoBackend, which uses a request-controlled num_frames value without an effective ceiling (CWE-770). An unauthenticated remote attacker can send requests to /v1/chat/completions or /tokenize selecting the openpangu video backend with a very large num_frames value. This forces large allocations and CPU work that can exhaust memory and crash the API server.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

vLLM 0.30.0 before 0.31.0 contains a resource exhaustion vulnerability in OpenCVDynamicOpenPanguVideoBackend, which uses request-controlled num_frames without an effective ceiling. Unauthenticated attackers can send /v1/chat/completions or /tokenize requests selecting the openpangu video_backend with a huge num_frames, forcing np.linspace allocations and CPU work that OOM-kill the API server.

Why it matters now

EPSS 0.00318 25th percentileScored 2026-11-16
Fix Fixed vllm (vllm-project): 0.31.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
vllm-projectvllm0.30.0 to before 0.31.00.31.0Patch availableCNA
  • vllm Vendorvllm-project Affected 0.30.0 to before 0.31.0 Fixed in 0.31.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:vllm:vllm:*:*:*:*:*:*:*:*——vLLM
  • cpe:2.3:a:vllm:vllm:*:*:*:*:*:*:*:* Versions — — ·vLLM

Remediation

Upgrade vllm-project vLLM to version 0.31.0 or later, which is the fixed version listed for this flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA vllm (vllm-project) Fixed in 0.31.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    vllm-project vllm 0.31.0

    5 records Highest priority Priority LOW 5 LOW

    Other records, highest priority first

    • TI-2026-91290 vLLM Cohere2 Vision denial of service via max_patchesPriority LOW 38
    • TI-2026-91289 Resource exhaustion in vLLM MiniMax M3 via min_pixelsPriority LOW 37
    • TI-2026-91288 Information disclosure in vLLM sanitize_message() leaks heap addressesPriority LOW 36

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-126394
  2. 2026-11-13 Alias added: GHSA-cj94-896r-fxx6

References

  • TI-2024-10229 Remote Code Execution in vllm-project/vllm CVSS 3.0CRITICAL 9.8
  • TI-2024-08404 Remote Code Execution in vllm-project/vllm CVSS 3.1CRITICAL 9.8
  • TI-2026-36017 vLLM: OpenAI auth bypass CVSS 3.1CRITICAL 9.1
  • TI-2026-63056 vLLM before 0.28.0 Denial of Service via negative token ID CVSS 4.0HIGH 8.7
  • TI-2026-04308 Hardcoded trust_remote_code=True in vllm-project/vllm Bypasses User Security Control CVSS 3.0HIGH 8.8
  • TI-2026-39137 vLLM: Remote DoS in vLLM via Invalid Recovered Token Reinjection CVSS 3.1HIGH 7.5
See all 131 →

Sources