Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
vLLM versions >=0.15.1 and <0.17.0 are affected by an SSRF protection bypass in the load_from_url_async method. The SSRF fix validates hostnames with urllib3 while the actual request is made with aiohttp, which parses URLs with yarl, and the two parse backslashes differently, so a crafted URL can pass validation and reach an arbitrary host. An attacker who can supply URLs to this function may be able to reach internal or external services. Upgrade to vLLM 0.17.0 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.1 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0060, the 49th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:42 UTC First seen by agentprime
- 31 Oct 2026, 14:42 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-v359-jj2v-j536
- OSV: GHSA-v359-jj2v-j536
- github.com/vllm-project/vllm/security/advisories/GHSA-qh4c-xf7m-gxfc
- github.com/vllm-project/vllm/security/advisories/GHSA-v359-jj2v-j536
- nvd.nist.gov/vuln/detail/CVE-2026-25960
- github.com/vllm-project/vllm/pull/34743
- github.com/vllm-project/vllm/commit/6f3b2047abd4a748e3db4a68543f8221358002c0
- access.redhat.com/errata/RHSA-2026:24977
- access.redhat.com/security/cve/CVE-2026-25960
- bugzilla.redhat.com/show_bug.cgi?id=2445892
- github.com/advisories/GHSA-v359-jj2v-j536
- github.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2026-3411.yaml
- github.com/vllm-project/vllm
- pypi.org/project/vllm