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.
CVE-2026-25960
CRITICALNVD 9.89.8
EchelonGraph scoreLOW confidence
This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8(low)
- EPSS
- 38.3%
- KEV
- Not listed
Published
March 9, 2026
Last Modified
June 30, 2026
Advisory Details (8)
Auto-updated Jun 30, 2026Patch available. Sources: github_commit, github_pr, github, redhat.
redhat Patch Available
redhat
2445892 – (CVE-2026-25960) CVE-2026-25960 vLLM: vLLM: Server-Side Request Forgery bypass via inconsistent URL parsing
https://bugzilla.redhat.com/show_bug.cgi?id=2445892redhat Patch Available
github Patch Available
SSRF Protection Bypass in vLLM · Advisory · vllm-project/vllm · GitHub
https://github.com/vllm-project/vllm/security/advisories/GHSA-v359-jj2v-j536github Patch Available
Server-Side Request Forgery (SSRF) in `MediaConnector` · Advisory · vllm-project/vllm · GitHub
https://github.com/vllm-project/vllm/security/advisories/GHSA-qh4c-xf7m-gxfcgithub_pr
[Core] Fix SSRF bypass via backslash-@ URL parsing inconsistency
Fix merged in vllm-project/vllm PR #34743 on 2026-02-18 — awaiting tagged release
https://github.com/vllm-project/vllm/pull/34743github_commit
commit 6f3b2047abd4 (vllm-project/vllm)
Fix landed in vllm-project/vllm commit 6f3b2047abd4 — awaiting tagged release
https://github.com/vllm-project/vllm/commit/6f3b2047abd4a748e3db4a68543f8221358002c0Vendor Advisories for CVE-2026-25960(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rhoai/odh-vllm-gaudi-rhel9:1780069069 | 2026-06-10 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vllm | 0.15.1, 0.16.0 | 0.17.0 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 04:40 UTCEG score recompute
- 2026-06-30 04:40 UTCVendor advisory
- 2026-06-30 04:31 UTCNVD updatefirst tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-25960?
CVE-2026-25960 is a critical vulnerability published on March 9, 2026. 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 loadfromurlasync method due to inconsistent URL parsing behavior between the validation layer and the actual HTTP client. The SSRF fix uses…
When was CVE-2026-25960 disclosed?
CVE-2026-25960 was first published in the National Vulnerability Database on March 9, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25960 actively exploited?
CVE-2026-25960 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 38.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-25960?
CVE-2026-25960 has a CVSS v3 base score of 9.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-25960?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25960, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25960
Is Your Infrastructure Affected by CVE-2026-25960?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.