vLLM up to 0.14.0 MediaConnector server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in vLLM up to 0.14.0. This issue affects the function MediaConnector. Executing a manipulation can lead to server-side request forgery.
This vulnerability appears as CVE-2026-24779. The attack may be performed from remote. There is no available exploit.
Upgrading the affected component is recommended.
Details
A vulnerability has been found in vLLM up to 0.14.0 and classified as critical. This vulnerability affects the function MediaConnector. The manipulation with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
vLLM is an inference and serving engine for large language models (LLMs). Prior to version 0.14.1, a Server-Side Request Forgery (SSRF) vulnerability exists in the `MediaConnector` class within the vLLM project's multimodal feature set. The load_from_url and load_from_url_async methods obtain and process media from URLs provided by users, using different Python parsing libraries when restricting the target host. These two parsing libraries have different interpretations of backslashes, which allows the host name restriction to be bypassed. This allows an attacker to coerce the vLLM server into making arbitrary requests to internal network resources. This vulnerability is particularly critical in containerized environments like `llm-d`, where a compromised vLLM pod could be used to scan the internal network, interact with other pods, and potentially cause denial of service or access sensitive data. For example, an attacker could make the vLLM pod send malicious requests to an internal `llm-d` management endpoint, leading to system instability by falsely reporting metrics like the KV cache state. Version 0.14.1 contains a patch for the issue.
The advisory is available at github.com. This vulnerability was named CVE-2026-24779 since 01/26/2026. The exploitation appears to be easy. The attack can be initiated remotely. Technical details are known, but there is no available exploit.
Upgrading to version 0.14.1 eliminates this vulnerability. Applying the patch f46d576c54fb8aeec5fc70560e850bed38ef17d7 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at EUVD (EUVD-2026-4711) and CERT Bund (WID-SEC-2026-0233). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Affected
- Open Source vllm
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.5
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.1
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: vLLM 0.14.1
Patch: f46d576c54fb8aeec5fc70560e850bed38ef17d7
Timeline
01/26/2026 CVE reserved01/28/2026 Advisory disclosed
01/28/2026 VulDB entry created
01/28/2026 VulDB entry last update
Sources
Advisory: GHSA-qh4c-xf7m-gxfcStatus: Confirmed
CVE: CVE-2026-24779 (🔒)
GCVE (CVE): GCVE-0-2026-24779
GCVE (VulDB): GCVE-100-343138
EUVD: 🔒
CERT Bund: WID-SEC-2026-0233 - vllm: Schwachstelle ermöglicht Offenlegung von Informationen und DoS
Entry
Created: 01/28/2026 07:59Updated: 01/28/2026 20:02
Changes: 01/28/2026 07:59 (66), 01/28/2026 16:04 (1), 01/28/2026 20:02 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.