CVE-2026-37237: vLLM · Uncontrolled Resource Consumption
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
AI-suggested
Until a fix is available, users should consider implementing controls to limit the size of fetched media responses or restrict the sources of media URLs to trusted domains to mitigate memory exhaustion risks.
Description
vLLM versions up to and including 0.17.0 contain a vulnerability that allows remote attackers to cause a Denial of Service (DoS) via memory exhaustion. This occurs because the AsyncMediaIO.fetch_audio and AsyncMediaIO.fetch_image functions fetch user-supplied media URLs without enforcing a maximum response size, enabling attackers to supply arbitrarily large files that exhaust server memory.