# CVE-2026-46561: pyLoad: SSRF via HTTP Redirect Bypass in parse_urls API

> An authenticated attacker can bypass private IP checks via HTTP redirects in the parse_urls API, enabling Server-Side Request Forgery against internal networks.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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:** Yes
- **Published:** 28 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-8rp3-xc6w-5qp5, PYSEC-2026-2991

## What is CVE-2026-46561?

CVE-2026-46561 is a medium-severity server-side request forgery vulnerability in pyload, published on 28 May 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. Prior to 0.5.0b3.dev100, the PREREQFUNCTION-based private IP check was not applied to HTTPRequest (used by the parse_urls API). An authenticated attacker can supply a URL pointing to an attacker-controlled server that responds with a 302 redirect to an internal/private IP address, bypassing the is_global_host() check on the initial URL. This vulnerability is fixed in 0.5.0b3.dev100.

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

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

3 open source packages ship an affected version, including pyload-ng.


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

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

Upgrade pyload-ng to 0.5.0b3.dev100 or later.

## Is CVE-2026-46561 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46561 is a medium-severity server-side request forgery vulnerability in pyload, published on 28 May 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-46561 exists.

Affected packages and fixed versions:
- pyload-ng (PyPI): affected all versions; fixed in 0.5.0b3.dev100
- pyload-ng (PyPI): affected all versions; fixed in 0.5.0b3.dev100
- pyload-ng (PyPI): affected all versions; fixed in 0.5.0b3.dev100

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-46561/ (Markdown: https://insights.sbomify.com/CVE-2026-46561/index.md)
```

## Sources

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

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