pyLoad: SSRF in parse_urls API endpoint via unvalidated URL parameter

Exploitation

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

CVSS

7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2026-35187: 0.28% estimated exploitation activity in the next 30 days; percentile 20.45 (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.

Vulnerability Details CWE-918: Server-Side Request Forgery (SSRF) The parseurls API function in src/pyload/core/api/init.py (line 556) fetches arbitrary URLs server-side via geturl(url) (pycurl) without any URL validation, protocol restriction, or IP blacklist. An authenticated user with ADD permission can: - Make HTTP/HTTPS requests to internal network resources and cloud metadata endpoints - Read local files via file:// protocol (pycurl reads the file server-side) - Interact with internal services via gopher:// and dict:// protocols - Enumerate file existence via error-based oracle (error 37 vs empty response) Vulnerable Code src/pyload/core/api/init.py (line 556): No validation is applied to the url parameter. The underlying pycurl supports file://, gopher://, dict://, and other dangerous protocols by default. Steps to Reproduce Setup Log in as any user with ADD permission and extract the CSRF token: PoC 1: Out-of-Band SSRF (HTTP/DNS exfiltration) Result: 7 DNS/HTTP interactions…

Published by the source

4 Apr 2026, 04:18 UTC

Last modified by the source

13 Jul 2026, 16:42 UTC

Source last checked

26 Oct 2026, 13:40 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2wvg-62qm-gj33

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-2wvg-62qm-gj33

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

# Patch Next advisory brief: CVE-2026-35187

Advisory: pyLoad: SSRF in parse_urls API endpoint via unvalidated URL parameter
IDs: CVE-2026-35187, GHSA-2wvg-62qm-gj33
Record: https://patchnext.com/advisories/cve-2026-35187 (revision 2, source checked 26 Oct 2026, 13:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI pyload-ng: affected <= 0.5.0b3.dev96

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pyload-ng.
- 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-2wvg-62qm-gj33 (OSV record GHSA-2wvg-62qm-gj33 lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev96)
- Verified: https://github.com/advisories/GHSA-2wvg-62qm-gj33 (GitHub-reviewed advisory GHSA-2wvg-62qm-gj33 lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev96)

Commands are suggestions: review each one before running it.