Quick answers
- Is CVE-2026-25960 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-25960 being exploited in the wild.
- How severe is CVE-2026-25960?
- High severity, with a CVSS score of 7.1, published 9 March 2026.
- Which products and versions are affected?
- vllm (PyPI) ECOSYSTEM:introduced=0.15.1,fixed=0.17.0.
- Is there a fix for CVE-2026-25960?
- Yes. vllm (PyPI): upgrade to 0.17.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-25960 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-25960?
- Check whether you run vllm (PyPI) or Vllm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- vllm (PyPI): upgrade to 0.17.0 or later
pip install "vllm>=0.17.0"
Technical details
A Server-Side Request Forgery (SSRF) bypass exists in vLLM's 'load_from_url_async' function within 'vllm/connections.py'. The vulnerability stems from a differential in how the 'urllib3' library (used for validation) and the 'yarl' library (used by 'aiohttp' for the actual request) parse backslashes in URLs. Specifically, 'urllib3' treats a backslash as part of the path, while 'yarl' may interpret it as part of the userinfo component, allowing an attacker to provide a URL that passes hostname allowlist checks but resolves to a different, malicious host during execution. This allows authenticated users to perform SSRF attacks against internal or external services. The issue is fixed in version 0.17.0.
Affected products
- vllm-project vllm >= 0.15.1, < 0.17.0
Identifiers
- CVE-2026-25960
- GHSA-v359-jj2v-j536
- PYSEC-2026-3411
Timeline
- 2026-03-09: disclosed
- 2026-03-09: advisory
- 2026-03-09: patched: Fixed in version 0.17.0
References
- https://api.github.com/users/RacerZ-fighting
- https://github.com/RacerZ-fighting
- https://api.github.com/users/RacerZ-fighting/gists%7B/gist_id%7D
- https://api.github.com/users/RacerZ-fighting/repos
- https://avatars.githubusercontent.com/u/78632303?v=4
- https://api.github.com/users/RacerZ-fighting/events%7B/privacy%7D