# CVE-2026-35459: pyLoad has SSRF fix bypass via HTTP redirect

> Authenticated users can bypass SSRF protections in pyLoad by using HTTP redirects to access internal network resources.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA: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-7gvf-3w72-p2pg, PYSEC-2026-495

## What is CVE-2026-35459?

CVE-2026-35459 is a critical 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, pyLoad has a server-side request forgery (SSRF) vulnerability. The fix for CVE-2026-33992 added IP validation to BaseDownloader.download() that checks the hostname of the initial download URL. However, pycurl is configured with FOLLOWLOCATION=1 and MAXREDIRS=10, causing it to automatically follow HTTP redirects. Redirect targets are never validated against the SSRF filter. An authenticated user with ADD permission can bypass the SSRF fix by submitting a URL that redirects to an internal address.

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

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

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-35459?

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

## Is CVE-2026-35459 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35459 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-35463](https://insights.sbomify.com/CVE-2026-35463/): pyLoad has Improper Neutralization of Special Elements used in an OS Command (high 8.8)
- [CVE-2026-33511](https://insights.sbomify.com/CVE-2026-33511/): pyload-ng: Authentication Bypass via Host Header Injection in ClickNLoad (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-35459 is a critical 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-35459 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-35459/ (Markdown: https://insights.sbomify.com/CVE-2026-35459/index.md)
```

## Sources

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

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