# CVE-2026-35187: pyLoad has SSRF in parse_urls API endpoint via unvalidated URL parameter

> Authenticated attackers can exploit unvalidated URL parameters in pyLoad to access internal network resources and local files via Server-Side Request Forgery.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-2wvg-62qm-gj33, PYSEC-2026-2988

## What is CVE-2026-35187?

CVE-2026-35187 is a high-severity server-side request forgery vulnerability in pyload, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

pyLoad is a free and open-source download manager written in Python. In 0.5.0b3.dev96 and earlier, the parse_urls API function in src/pyload/core/api/__init__.py fetches arbitrary URLs server-side via get_url(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, and enumerate file existence via error-based oracle (error 37 vs empty response).

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-35187?

3 open source packages ship an affected version, including pyload-ng. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyload-ng` | PyPI | All versions to 0.5.0b3.dev96 | None |
| `pyload-ng` | PyPI | All versions to 0.5.0b3.dev96 | None |
| `pyload-ng` | PyPI | All versions to 0.5.0b3.dev96 | None |

Products: Pyload-Ng Project Pyload-Ng.

## How do I fix CVE-2026-35187?

No fix has been published for CVE-2026-35187 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-35187 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35187 exists.

## Other vulnerabilities in pyload

- [CVE-2025-54802](https://insights.sbomify.com/CVE-2025-54802/): pyLoad CNL Blueprint is vulnerable to Path Traversal through `dlc_path` leading to Remote Code Execution (RCE) (critical 9.8)
- [CVE-2024-22416](https://insights.sbomify.com/CVE-2024-22416/): Cross-Site Request Forgery on any API call in pyLoad may lead to admin privilege escalation (critical 9.7)
- [CVE-2023-0488](https://insights.sbomify.com/CVE-2023-0488/): Cross-site Scripting (XSS) - Stored in pyload/pyload (critical 9.6)
- [CVE-2026-35459](https://insights.sbomify.com/CVE-2026-35459/): pyLoad has SSRF fix bypass via HTTP redirect (critical 9.3)
- [CVE-2026-35463](https://insights.sbomify.com/CVE-2026-35463/): pyLoad has Improper Neutralization of Special Elements used in an OS Command (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35187 and fix it if it is affected.

What it is: CVE-2026-35187 is a high-severity server-side request forgery vulnerability in pyload, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35187 exists.

Affected packages and fixed versions:
- pyload-ng (PyPI): affected all versions up to 0.5.0b3.dev96; no fix listed
- pyload-ng (PyPI): affected all versions up to 0.5.0b3.dev96; no fix listed
- pyload-ng (PyPI): affected all versions up to 0.5.0b3.dev96; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35187/ (Markdown: https://insights.sbomify.com/CVE-2026-35187/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35187
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35187
- OSV: https://osv.dev/vulnerability/CVE-2026-35187

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35187/
Summaries are generated and may contain mistakes; the official description above is the record.