CVE-2026-25960
Vllm server-side request forgery (SSRF)
- Published9 Mar 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:LAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:24977
- https://access.redhat.com/errata/RHSA-2026:42644
- https://access.redhat.com/security/cve/CVE-2026-25960
- https://bugzilla.redhat.com/show_bug.cgi?id=2445892
- https://github.com/vllm-project/vllm/commit/6f3b2047abd4a748e3db4a68543f8221358002c0
- https://github.com/vllm-project/vllm/pull/34743
- https://github.com/vllm-project/vllm/security/advisories/GHSA-qh4c-xf7m-gxfc
- https://github.com/vllm-project/vllm/security/advisories/GHSA-v359-jj2v-j536
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25960.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-25960 being actively exploited?
CVE-2026-25960 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.75%.
How severe is CVE-2026-25960?
CVE-2026-25960 has a CVSS 3.1 base score of 7.1, rated high. EPSS estimates a 0.75% probability of exploitation.
Which products are affected by CVE-2026-25960?
Affected products include Vllm.
How do I fix CVE-2026-25960?
Upgrade affected software to a fixed version, for example Vllm 0.17.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-25960 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.