# CVE-2026-37237: Denial of service in n/a

> Remote attackers can cause denial of service in vLLM by providing URLs to arbitrarily large media files, exhausting server memory.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-63mw-rppr-f2pf

## What is CVE-2026-37237?

CVE-2026-37237 is a high-severity denial of service vulnerability in Vllm Vllm, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-37237?

It affects 1 product.


Products: Vllm Vllm.

## How do I fix CVE-2026-37237?

No fix has been published for CVE-2026-37237 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-37237 being exploited?

There is no known exploitation of CVE-2026-37237 in the wild and no public exploit code.

## Other vulnerabilities in Vllm Vllm

- [CVE-2025-32444](https://insights.sbomify.com/CVE-2025-32444/): vLLM Vulnerable to Remote Code Execution via Mooncake Integration (critical 10.0)
- [CVE-2026-22778](https://insights.sbomify.com/CVE-2026-22778/): vLLM leaks a heap address when PIL throws an error (critical 9.8)
- [CVE-2025-47277](https://insights.sbomify.com/CVE-2025-47277/): vLLM Allows Remote Code Execution via PyNcclPipe Communication Service (critical 9.8)
- [CVE-2024-11041](https://insights.sbomify.com/CVE-2024-11041/): Remote Code Execution in vllm-project/vllm (critical 9.8)
- [CVE-2026-48746](https://insights.sbomify.com/CVE-2026-48746/): vLLM: OpenAI auth bypass (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-37237 and fix it if it is affected.

What it is: CVE-2026-37237 is a high-severity denial of service vulnerability in Vllm Vllm, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-37237 in the wild and no public exploit code.

Affected product: Vllm Vllm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-37237/ (Markdown: https://insights.sbomify.com/CVE-2026-37237/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-37237
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-37237
- OSV: https://osv.dev/vulnerability/CVE-2026-37237

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-37237/
Summaries are generated and may contain mistakes; the official description above is the record.