CVE-2026-24779: CWE-918: Server-Side Request Forgery (SSRF) in vllm-project vllm
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.
AI Analysis
Technical Summary
The vLLM project, an inference and serving engine for large language models, contains a Server-Side Request Forgery (SSRF) vulnerability (CWE-918) in its MediaConnector class before version 0.14.1. The vulnerability stems from the use of two different Python parsing libraries in the load_from_url and load_from_url_async methods, which interpret backslashes differently. This discrepancy allows attackers to bypass hostname restrictions and force the vLLM server to make arbitrary requests to internal network resources. In containerized deployments such as llm-d, exploitation could enable scanning of internal networks, interaction with other pods, and denial of service or unauthorized access to sensitive data. The vulnerability is patched in version 0.14.1.
Potential Impact
Successful exploitation allows an attacker with limited privileges to bypass hostname restrictions and coerce the vLLM server into making arbitrary HTTP requests to internal network resources. This can lead to unauthorized internal network scanning, interaction with other containerized services, denial of service by sending malicious requests to management endpoints, and potential exposure of sensitive data. The vulnerability has a CVSS 3.1 score of 7.1 (high severity), indicating a significant impact on confidentiality and availability.
Mitigation Recommendations
A patch addressing this SSRF vulnerability is available in vLLM version 0.14.1. Users should upgrade to version 0.14.1 or later to remediate the issue. Since this is not a cloud service, remediation requires applying the official fix. Refer to the vendor advisories, including Red Hat's security advisories, for detailed update instructions and confirmation of the fix.
CVE-2026-24779: CWE-918: Server-Side Request Forgery (SSRF) in vllm-project vllm
Description
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.
CVSS v3.1
Score 7.1high
Affected software
vllm-project
vllm
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vLLM project, an inference and serving engine for large language models, contains a Server-Side Request Forgery (SSRF) vulnerability (CWE-918) in its MediaConnector class before version 0.14.1. The vulnerability stems from the use of two different Python parsing libraries in the load_from_url and load_from_url_async methods, which interpret backslashes differently. This discrepancy allows attackers to bypass hostname restrictions and force the vLLM server to make arbitrary requests to internal network resources. In containerized deployments such as llm-d, exploitation could enable scanning of internal networks, interaction with other pods, and denial of service or unauthorized access to sensitive data. The vulnerability is patched in version 0.14.1.
Potential Impact
Successful exploitation allows an attacker with limited privileges to bypass hostname restrictions and coerce the vLLM server into making arbitrary HTTP requests to internal network resources. This can lead to unauthorized internal network scanning, interaction with other containerized services, denial of service by sending malicious requests to management endpoints, and potential exposure of sensitive data. The vulnerability has a CVSS 3.1 score of 7.1 (high severity), indicating a significant impact on confidentiality and availability.
Mitigation Recommendations
A patch addressing this SSRF vulnerability is available in vLLM version 0.14.1. Users should upgrade to version 0.14.1 or later to remediate the issue. Since this is not a cloud service, remediation requires applying the official fix. Refer to the vendor advisories, including Red Hat's security advisories, for detailed update instructions and confirmation of the fix.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-01-26T21:06:47.869Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-24779","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:3461","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:3462","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:30089","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:30088","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:30087","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:10184","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:3782","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:19712","vendor":"Red Hat"}]
Threat ID: 697936c84623b1157c4a64f3
Added to database: 01/27/2026, 22:06:00 UTC
Last enriched: 07/22/2026, 22:30:46 UTC
Last updated: 09/10/2026, 22:18:13 UTC
Views: 563
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.