vLLM up to and including 0.17.0 allows remote attackers to cause a Denial of Service via memory exhaustion. The AsyncMediaIO.fetch_audio and AsyncMediaIO.fetch_image functions in multimodal/inputs.py fetch user-supplied media URLs using aiohttp and call r.read() without enforcing a maximum response size, allowing an attacker to exhaust server memory by providing a URL to an arbitrarily large file.
CVE-2026-37237
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 43%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (3)
Auto-updated Aug 28, 2026[Docs] Expand --allowed-media-domains security guidance with threat details
Fix merged in vllm-project/vllm PR #36506 on 2026-03-09 — awaiting tagged release
https://github.com/vllm-project/vllm/pull/36506vllm/vllm/multimodal/inputs.py at main · vllm-project/vllm · GitHub
https://github.com/vllm-project/vllm/blob/main/vllm/multimodal/inputs.pyVendor Advisories for CVE-2026-37237(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 23:59 UTCGHSA enrichment
- 2026-08-29 11:25 UTCEG score recompute
- 2026-08-29 11:24 UTCGHSA enrichment
- 2026-08-28 22:48 UTCGHSA enrichment
- 2026-08-28 22:03 UTCEG score recompute▲ 7.50
- 2026-08-28 22:03 UTCGHSA enrichment
- 2026-08-28 21:59 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-08-28 16:29 UTCNVD update
- 2026-08-28 15:31 UTCEG score recompute
- 2026-08-28 15:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-400
Frequently asked(5)
What is CVE-2026-37237?
When was CVE-2026-37237 disclosed?
Is CVE-2026-37237 actively exploited?
What is the CVSS score of CVE-2026-37237?
How do I remediate CVE-2026-37237?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-37237
Is Your Infrastructure Affected by CVE-2026-37237?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.