# CVE-2026-33992: pyLoad: Server-Side Request Forgery via Download Link Submission Enables Cloud Metadata Exfiltration

> An authenticated attacker can exploit SSRF in pyLoad to access internal services and exfiltrate sensitive cloud metadata from the host environment.

- **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:** 27 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-m74m-f7cr-432x, PYSEC-2026-497

## What is CVE-2026-33992?

CVE-2026-33992 is a critical server-side request forgery vulnerability in pyload, published on 27 Mar 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 version 0.5.0b3.dev97, PyLoad's download engine accepts arbitrary URLs without validation, enabling Server-Side Request Forgery (SSRF) attacks. An authenticated attacker can exploit this to access internal network services and exfiltrate cloud provider metadata. On DigitalOcean droplets, this exposes sensitive infrastructure data including droplet ID, network configuration, region, authentication keys, and SSH keys configured in user-data/cloud-init. Version 0.5.0b3.dev97 contains a patch.

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

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

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 Pyload.

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

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

## Is CVE-2026-33992 being exploited?

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

## Other vulnerabilities in pyload

- [CVE-2023-0297](https://insights.sbomify.com/CVE-2023-0297/): Code Injection in pyload/pyload (critical 9.8)
- [CVE-2024-47821](https://insights.sbomify.com/CVE-2024-47821/): pyLoad vulnerable to remote code execution by download to /.pyload/scripts using /flashgot API (critical 9.1)
- [CVE-2024-32880](https://insights.sbomify.com/CVE-2024-32880/): pyLoad allows upload to arbitrary folder lead to RCE (critical 9.1)
- [CVE-2026-41133](https://insights.sbomify.com/CVE-2026-41133/): pyLoad has Stale Session Privilege After Role/Permission Change (Privilege Revocation Bypass) (high 8.8)
- [CVE-2023-47890](https://insights.sbomify.com/CVE-2023-47890/): Download to arbitrary folder can lead to RCE (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33992 is a critical server-side request forgery vulnerability in pyload, published on 27 Mar 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-33992 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-33992/ (Markdown: https://insights.sbomify.com/CVE-2026-33992/index.md)
```

## Sources

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

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