Skip to main content
VulnerabilityPublished

CVE-2026-130686: vllm · Uncontrolled Resource Consumption

Affects vllmSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 0.33.0 soon.

Data as of 18 Nov 2026, 12:20 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.17.5
Patch
Available – fixed in 0.33.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade vllm to 0.33.0.

Affected software

ProductAffectedFixed in
vllm-projectvllmAffected
  • >=0.6.0 <0.33.0
Fixed in
  • 0.33.0
PyPIvllmpkg:pypi/vllmOther threatsAffected
  • >=0.6.0 <0.33.0
Fixed in
  • 0.33.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade vLLM to version 0.33.0 or later, where this uncontrolled resource consumption vulnerability is fixed. No other mitigations are indicated.

Description

vLLM versions from 0.6.0 up to but not including 0.33.0 have an uncontrolled resource consumption vulnerability. Remote clients can submit many image URLs in a single request, causing the server to download and decode all images before prompt-length checks, exhausting memory, CPU, and connection resources. This can lead to denial of service. The issue is fixed in version 0.33.0.

References

Community reviews

Loading reviews…