vLLM has SSRF Protection Bypass

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

EPSS

• CVE-2026-25960: 0.57% estimated exploitation activity in the next 30 days; percentile 47.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The SSRF protection fix for https://github.com/vllm-project/vllm/security/advisories/GHSA-qh4c-xf7m-gxfc can be bypassed in the loadfromurlasync method due to inconsistent URL parsing behavior between the validation layer and the actual HTTP client. Affected Component - File: vllm/connections.py - Function: loadfromurlasync Vulnerability Details Root Cause The SSRF fix uses urllib3.util.parseurl() to validate and extract the hostname from user-provided URLs. However, loadfromurlasync 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.parseurl() | 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) |…

Published by the source

9 Mar 2026, 19:55 UTC

Last modified by the source

17 Jul 2026, 16:30 UTC

Source last checked

26 Oct 2026, 13:47 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-v359-jj2v-j536

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-v359-jj2v-j536

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-25960

Advisory: vLLM has SSRF Protection Bypass
IDs: CVE-2026-25960, GHSA-v359-jj2v-j536
Record: https://patchnext.com/advisories/cve-2026-25960 (revision 2, source checked 26 Oct 2026, 13:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: vllm 0.17.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI vllm: affected >= 0.15.1, < 0.17.0; fixed in 0.17.0

## Suggested inspection (read-only)
- `python -m pip show vllm`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on vllm.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-v359-jj2v-j536 (OSV record GHSA-v359-jj2v-j536 lists affected ranges: PyPI vllm >=0.15.1 <0.17.0 (fixed))
- Verified: https://github.com/advisories/GHSA-v359-jj2v-j536 (GitHub-reviewed advisory GHSA-v359-jj2v-j536 lists affected ranges: PyPI vllm >=0.15.1 <0.17.0)

Commands are suggestions: review each one before running it.