| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-v359-jj2v-j536 | vLLM has SSRF Protection Bypass |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Wed, 11 Mar 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-474 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Tue, 10 Mar 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 10 Mar 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Vllm-project
Vllm-project vllm |
|
| Vendors & Products |
Vllm-project
Vllm-project vllm |
Mon, 09 Mar 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | vLLM is an inference and serving engine for large language models (LLMs). The SSRF protection fix for CVE-2026-24779 add in 0.15.1 can be bypassed in the load_from_url_async method due to inconsistent URL parsing behavior between the validation layer and the actual HTTP client. The SSRF fix uses urllib3.util.parse_url() to validate and extract the hostname from user-provided URLs. However, load_from_url_async uses aiohttp for making the actual HTTP requests, and aiohttp internally uses the yarl library for URL parsing. This vulnerability in 0.17.0. | |
| Title | SSRF Protection Bypass in vLLM | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-10T15:01:18.476Z
Reserved: 2026-02-09T17:13:54.066Z
Link: CVE-2026-25960
Updated: 2026-03-10T15:01:15.560Z
Status : Awaiting Analysis
Published: 2026-03-09T21:16:15.537
Modified: 2026-03-11T13:53:47.157
Link: CVE-2026-25960
OpenCVE Enrichment
Updated: 2026-03-10T14:07:02Z
Github GHSA