CVE-2026-24779: vLLM Server-Side Request Forgery (SSRF) Vulnerability in MediaConnector

vllm Updated 28 Jan 2026

Summary

28/01/2026
Yes i
High
7.1

CVE-2026-24779: vLLM vulnerable to Server-Side Request Forgery (SSRF) through MediaConnector. Affects vllm versions < 0.14.1. Fixed in 0.14.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

vLLM is an open-source project designed for multimodal machine learning, enabling users to load and process various media types such as images, audio, and video. The project features a MediaConnector class that facilitates the fetching of media content from user-provided URLs. However, due to a vulnerability in its URL handling, vLLM is susceptible to Server-Side Request Forgery (SSRF) attacks, which can lead to unauthorized access to internal network resources.

Vulnerability Detail

The SSRF vulnerability in vLLM arises from the MediaConnector class's load_from_url and load_from_url_async methods. These methods utilize different URL parsing libraries that interpret backslashes differently, allowing attackers to bypass hostname restrictions. This flaw can enable an attacker to coerce the vLLM server into making arbitrary requests to internal resources, potentially leading to data exposure or denial of service. The vulnerability is particularly critical in containerized environments, where a compromised vLLM pod could scan the internal network and interact with other pods, causing instability and false reporting of metrics.

How To Fix

Latest published version: 0.32.0 as of 22 Oct 2026

pip install --upgrade "vllm==0.32.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.14.1

This is the first release that contains the fix.

pip install --upgrade "vllm==0.14.1"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, you can restrict the URLs that can be processed by the MediaConnector class by implementing additional validation checks before passing user-provided URLs to the load_from_url method. This can help mitigate the risk of SSRF attacks until the package is updated.

Conclusion

The vLLM package is vulnerable to a Server-Side Request Forgery (SSRF) due to improper URL handling in its MediaConnector class. It is crucial for users to update to version 0.14.1 or later to mitigate this risk. Additionally, utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for vllm →

Share this vulnerability

FAQ

The vulnerability is a Server-Side Request Forgery (SSRF) that allows attackers to make unauthorized requests to internal network resources.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Exploitation of this vulnerability can lead to unauthorized access to sensitive data, denial of service, and instability in containerized environments.

Yes, the vulnerability has been patched in version 0.14.1 of the vLLM package. It is recommended to update to this version.

The CVSS score of this vulnerability is 7.1, indicating a high severity level.

Related vulnerabilities

Recent vulnerabilities recorded for vllm.

How To Fix

Latest published version: 0.32.0 as of 22 Oct 2026

pip install --upgrade "vllm==0.32.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.14.1

This is the first release that contains the fix.

pip install --upgrade "vllm==0.14.1"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback