How broadly exploitable is this vulnerability?

Exploitability depends on exposure of the multimodal endpoints that accept user-provided URLs. In many deployments, these endpoints are reachable by untrusted clients (e.g., external applications, API consumers), which makes the issue broadly exploitable whenever users can supply arbitrary URLs to vLLM.

Does exploitation require authentication or internal access?

Not necessarily. If the vLLM API or any upstream service allows untrusted users to submit URLs to `MediaConnector`, an attacker only needs that level of access. The SSRF effect then allows them to leverage the vLLM pod's internal network position, even if they themselves have no direct access to those internal resources.

What is the safest general fix pattern?

The most robust pattern is to enforce a strict allowlist of permitted destinations and schemes, combined with a single canonical URL parsing routine that is used consistently for both validation and the outbound request. Complementary controls at the network layer should prevent the pod from reaching internal or sensitive endpoints that are not explicitly required.

Severity:

HIGH RISK

(7.1)

Server-Side Request Forgery (CWE-918) in vLLM MediaConnector Host Validation

CVE-2026-24779

Published:

Jan 27, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-78

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

Remote Code Execution

March 7, 2026

CWE-89

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Remote Code Execution via SQL Injection on the Database Server

March 7, 2026

Vulnerability Type

Category:

Server-Side Request Forgery (SSRF)

CWE:

CWE-918

Impact:

Unauthorized access to internal network resources via SSRF

Severity:

HIGH RISK

(7.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Server-Side Request Forgery (SSRF)

CWE:

CWE-918

Impact:

Unauthorized access to internal network resources via SSRF

Severity:

HIGH RISK

(7.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Server-Side Request Forgery (CWE-918) in vLLM MediaConnector Host Validation

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare