CVE-2026-25960

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 57% of all CVEs by exploit prediction. 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: epss, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

Published

March 9, 2026

Last Modified

July 21, 2026

Advisory Details (9)

Auto-updated Oct 3, 2026
Patch available. Sources: github, redhat, github_commit, github_pr.
redhat
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25960.json
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=2445892
redhat Patch Available

CVE-2026-25960 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-25960
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:42644
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:24977
github Patch Available

SSRF Protection Bypass in vLLM · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-v359-jj2v-j536
github 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-gxfc
github_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/34743
github_commit

commit 6f3b2047abd4 (vllm-project/vllm)

Fix landed in vllm-project/vllm commit 6f3b2047abd4 — awaiting tagged release

https://github.com/vllm-project/vllm/commit/6f3b2047abd4a748e3db4a68543f8221358002c0

Vendor Advisories for CVE-2026-25960(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-vllm-rocm-rhel9:17839988572026-07-21redhat
redhatrhoai/odh-vllm-gaudi-rhel9:17800690692026-06-10redhat

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)
PackageVulnerable rangeFix by version rangeDependents
vllm0.15.1, 0.16.0
  • 0.15.1 up to 0.17.0: fixed in 0.17.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 21× 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.

Showing the most recent 100 of 150 total refreshes for this CVE.

  1. 2026-10-05 17:42 UTCEPSS rescore
  2. 2026-10-04 23:21 UTCEPSS rescore
  3. 2026-10-03 14:25 UTCEPSS rescore
  4. 2026-10-01 19:49 UTCEPSS rescore
  5. 2026-09-30 15:03 UTCEPSS rescore
  6. 2026-09-28 13:51 UTCEPSS rescore
  7. 2026-09-26 15:58 UTCEPSS rescore
  8. 2026-09-26 00:26 UTCEPSS rescore
  9. 2026-09-22 01:45 UTCOSV refresh
  10. 2026-09-20 20:15 UTCEPSS rescore
  11. 2026-09-18 19:27 UTCEPSS rescore
  12. 2026-09-16 14:07 UTCEPSS rescore
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-13 16:47 UTCEPSS rescore
  15. 2026-09-12 15:01 UTCEPSS rescore
  16. 2026-09-11 14:52 UTCEPSS rescore
  17. 2026-09-10 09:34 UTCEPSS rescore
  18. 2026-09-08 22:00 UTCEPSS rescore
  19. 2026-09-07 16:01 UTCEPSS rescore
  20. 2026-09-06 13:47 UTCEPSS rescore
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-04 05:06 UTCEPSS rescore
  23. 2026-09-02 22:40 UTCOSV refresh
  24. 2026-09-02 14:11 UTCEPSS rescore
  25. 2026-09-01 13:53 UTCEPSS rescore
Show 75 more
  1. 2026-09-01 04:39 UTCEPSS rescore
  2. 2026-08-30 19:17 UTCEPSS rescore
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-25 13:48 UTCEPSS rescore
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-19 17:03 UTCEPSS rescore
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 12:10 UTCEG score recompute
  16. 2026-08-16 12:10 UTCVendor advisory
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-15 00:36 UTCVendor advisory
  20. 2026-08-14 20:22 UTCVendor advisory
  21. 2026-08-14 12:20 UTCVendor advisory
  22. 2026-08-14 08:06 UTCEG score recompute
  23. 2026-08-14 08:06 UTCVendor advisory
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-13 03:45 UTCVendor advisory
  26. 2026-08-12 23:31 UTCEG score recompute
  27. 2026-08-12 23:31 UTCVendor advisory
  28. 2026-08-12 13:50 UTCEPSS rescore
  29. 2026-08-12 02:19 UTCVendor advisory
  30. 2026-08-11 22:02 UTCEG score recompute
  31. 2026-08-11 22:02 UTCVendor advisory
  32. 2026-08-11 13:42 UTCEPSS rescore
  33. 2026-08-11 05:11 UTCEG score recompute
  34. 2026-08-11 05:11 UTCVendor advisory
  35. 2026-08-11 00:00 UTCEPSS rescore
  36. 2026-08-10 12:58 UTCVendor advisory
  37. 2026-08-10 06:53 UTCVendor advisory
  38. 2026-08-10 02:14 UTCVendor advisory
  39. 2026-08-09 21:59 UTCVendor advisory
  40. 2026-08-09 17:45 UTCEG score recompute
  41. 2026-08-09 17:45 UTCVendor advisory
  42. 2026-08-09 13:46 UTCEPSS rescore
  43. 2026-08-09 13:30 UTCVendor advisory
  44. 2026-08-09 07:46 UTCEG score recompute
  45. 2026-08-09 07:46 UTCVendor advisory
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-08 08:04 UTCVendor advisory
  48. 2026-08-08 03:49 UTCVendor advisory
  49. 2026-08-07 23:22 UTCVendor advisory
  50. 2026-08-07 19:08 UTCEG score recompute
  51. 2026-08-07 19:08 UTCVendor advisory
  52. 2026-08-06 20:08 UTCEG score recompute
  53. 2026-08-06 20:08 UTCVendor advisory
  54. 2026-08-06 13:46 UTCEPSS rescore
  55. 2026-08-06 06:29 UTCVendor advisory
  56. 2026-08-06 02:15 UTCEG score recompute
  57. 2026-08-06 02:15 UTCVendor advisory
  58. 2026-08-05 19:17 UTCEPSS rescore
  59. 2026-08-04 15:10 UTCEPSS rescore
  60. 2026-08-04 05:55 UTCVendor advisory
  61. 2026-08-04 01:40 UTCEG score recompute
  62. 2026-08-04 01:40 UTCVendor advisory
  63. 2026-08-03 10:36 UTCEPSS rescore
  64. 2026-08-03 02:28 UTCVendor advisory
  65. 2026-08-02 22:14 UTCVendor advisory
  66. 2026-08-02 17:59 UTCEG score recompute
  67. 2026-08-02 17:59 UTCVendor advisory
  68. 2026-08-02 02:26 UTCEPSS rescore
  69. 2026-08-01 04:16 UTCEPSS rescore
  70. 2026-07-30 16:27 UTCEPSS rescore
  71. 2026-07-30 01:30 UTCEPSS rescore
  72. 2026-07-28 15:36 UTCEPSS rescore
  73. 2026-07-26 14:54 UTCEPSS rescore
  74. 2026-07-26 14:54 UTCEPSS rescore
  75. 2026-07-25 14:18 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

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 on March 9, 2026, with the most recent update on July 21, 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 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-25960?
CVE-2026-25960 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-25960?
A fix for CVE-2026-25960 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-25960 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25960

Explore →

Is Your Infrastructure Affected by CVE-2026-25960?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs