CVE-2026-73560

Received Received - Intake

Server-Side Request Forgery in vLLM Prior to 0.26.0

Publication date: 2026-08-17

Last updated on: 2026-08-17

Assigner: GitHub, Inc.

Description

vLLM is an inference and serving engine for large language models. Prior to 0.26.0, the MiMoV2OmniMultiModalProcessor in vllm/transformers_utils/processors/mimo_v2_omni.py passes attacker-controlled image and audio strings through _fetch_image, requests.get, and Image.open instead of MediaConnector, bypassing allowed_media_domains and allowed_local_media_path protections and allowing server-side requests and reads of arbitrary files accessible to the vLLM process. This issue is fixed in version 0.26.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-17

Last Modified

2026-08-17

Generated

2026-08-18

AI Q&A

2026-08-18

EPSS Evaluated

N/A

NVD

CVE-2026-73560

EUVD

EUVD-2026-60377

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-918	The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

Executive Summary

This vulnerability in vLLM before version 0.26.0 allows attackers to bypass security checks by passing malicious image and audio strings through functions like _fetch_image, requests.get, and Image.open. Instead of using the intended MediaConnector, it directly processes these files, enabling server-side requests and arbitrary file reads accessible to the vLLM process.

Impact Analysis

An attacker could exploit this to read sensitive files on the server where vLLM is running, potentially exposing confidential data like configuration files, credentials, or other restricted information. This could lead to data breaches or unauthorized access to system resources.

Compliance Impact

This vulnerability could violate compliance requirements such as GDPR or HIPAA by enabling unauthorized access to personal or sensitive data. Organizations using affected vLLM versions may face legal penalties, reputational damage, and increased scrutiny for failing to protect data adequately.

Mitigation Strategies

Upgrade vLLM to version 0.26.0 or later to address the vulnerability in the MiMoV2OmniMultiModalProcessor component.

Hi! I’m here to help you understand CVE-2026-73560. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70