vLLM up to 0.17.0 Media Fetching multimodal/inputs.py AsyncMediaIO.fetch_audio/AsyncMediaIO.fetch_image memory allocation

Summaryinfo

A vulnerability was found in vLLM up to 0.17.0. It has been classified as problematic. Affected by this vulnerability is the function AsyncMediaIO.fetch_audio/AsyncMediaIO.fetch_image of the file multimodal/inputs.py of the component Media Fetching. The manipulation leads to memory allocation. This vulnerability is uniquely identified as CVE-2026-37237. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in vLLM up to 0.17.0. It has been rated as problematic. This issue affects the function AsyncMediaIO.fetch_audio/AsyncMediaIO.fetch_image of the file multimodal/inputs.py of the component Media Fetching. The manipulation with an unknown input leads to a memory allocation vulnerability. Using CWE to declare the problem leads to CWE-789. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. Impacted is availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-37237 since 04/06/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• vLLM

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7
• 0.8
• 0.9
• 0.10
• 0.11
• 0.12
• 0.13
• 0.14
• 0.15
• 0.16
• 0.17.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion