vLLM has SSRF Protection Bypass
Published 9 Mar 2026 · Updated 17 Jul 2026
Is your project on an affected vllm?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=0.15.1 <0.17.0
- Fixed in
- 0.17.0
pip install 'vllm>=0.17.0'Details
Summary
The SSRF protection fix for https://github.com/vllm-project/vllm/security/advisories/GHSA-qh4c-xf7m-gxfc 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.
Affected Component
- File:
vllm/connections.py - Function:
load_from_url_async
Vulnerability Details
Root Cause
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.
These two URL parsers handle backslash characters (\) differently:
| Parser | Input URL | Parsed Host | Parsed Path | Behavior |
|--------|-----------|-------------|-------------|----------|
| urllib3.parse_url() | https://httpbin.org\@evil.com/ | httpbin.org | /%5C@evil.com/ | URL-encodes \ as %5C, treats \@evil.com/ as part of the path |
| yarl (via aiohttp) | https://httpbin.org\@evil.com/ | evil.com | / | Treats \ as part of userinfo (user: httpbin.org\), the @ acts as the userinfo/host separator |
Attack Scenario
# Attacker provides this URL
malicious_url = "https://httpbin.org\\@evil.com/"
# 1. Validation layer (urllib3.parse_url)
parsed = urllib3.util.parse_url(malicious_url)
# parsed.host == "httpbin.org" ✅ Passes validation
# 2. Actual request (aiohttp with yarl)
async with aiohttp.ClientSession() as session:
async with session.get(malicious_url) as response:
# Request actually goes to evil.com! ❌ Bypass!Why This Happens
1. yarl: Interprets httpbin.org\ as the userinfo component, and @ as the userinfo/host separator, so the URL is parsed as user=httpbin.org\, host=evil.com, path=/
2. urllib3: URL-encodes the backslash as %5C, so \@evil.com/ becomes /%5C@evil.com/ which is treated as part of the path, leaving host=httpbin.org
This inconsistency allows an attacker to:
- Bypass the hostname allowlist check
- Access arbitrary internal/external services
- Perform full SSRF attacks
Fixes
- https://github.com/vllm-project/vllm/pull/34743
Is GHSA-v359-jj2v-j536 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected vllm, and gives you the command that fixes it.
More advisories for vllm
- LowCVE-2026-115917vLLM: Permissive default CORS origins allow cross-origin requests to the vLLM HTTP server · 28 Oct 2026
- MediumCVE-2026-115913vLLM: Phi-4 multimodal audio encoder materializes and retains full attention matrices: a single max-length audio OOM-crashes the vLLM engine · 28 Oct 2026
- MediumCVE-2026-115914vLLM DeepSeek-OCR image processing vulnerable to denial of service · 28 Oct 2026
- HighCVE-2026-115915vLLM: Untrusted EPS inputs can trigger denial of service or Ghostscript RCE · 28 Oct 2026
- HighCVE-2026-115912vLLM: Public multimodal SHM handle forgery reaches worker-side `pickle.loads()` with insecure serialization disabled · 28 Oct 2026
- MediumCVE-2026-115916vLLM: Out-of-vocabulary prompt token id passes input validation and triggers a CUDA device-side assert (engine crash / DoS) · 28 Oct 2026
References
- Linkgithub.com/vllm-project/vllm/security/advisories/GHSA-qh4c-xf7m-gxfc
- Linkgithub.com/vllm-project/vllm/security/advisories/GHSA-v359-jj2v-j536
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-25960
- Linkgithub.com/vllm-project/vllm/pull/34743
- Linkgithub.com/vllm-project/vllm/commit/6f3b2047abd4a748e3db4a68543f8221358002c0
- Linkaccess.redhat.com/errata/RHSA-2026:24977
- Linkaccess.redhat.com/security/cve/CVE-2026-25960
- Linkbugzilla.redhat.com/show_bug.cgi?id=2445892
- Advisorygithub.com/advisories/GHSA-v359-jj2v-j536
- Linkgithub.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2026-3411.yaml
- Packagegithub.com/vllm-project/vllm
- Linkpypi.org/project/vllm
- Linksecurity.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25960.json
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.