# CVE-2026-44226: pyLoad: Unauthenticated traceback disclosure via global exception handler in WebUI

> Unauthenticated attackers can trigger server exceptions to view internal Python stack traces, exposing sensitive application details.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-c3gc-9pf2-84gg, PYSEC-2026-2993

## What is CVE-2026-44226?

CVE-2026-44226 is a medium-severity vulnerability in pyload, published on 11 May 2026. An attacker can exploit it over the internet without logging in, 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, pyload-ng WebUI returns full Python traceback details to clients on unhandled exceptions. Because /web/<path:filename> is reachable without authentication and renders attacker-controlled template names, an unauthenticated user can reliably trigger a server exception (for example by requesting a non-existent template) and receive internal stack traces in the HTTP response. This vulnerability is fixed in 0.5.0b3.dev100.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

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 | 0.5.0b3.dev100 |
| `pyload-ng` | PyPI | All versions | 0.5.0b3.dev100 |
| `pyload-ng` | PyPI | All versions | 0.5.0b3.dev100 |

Products: Pyload Pyload.

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

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

## Is CVE-2026-44226 being exploited?

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

## Other vulnerabilities in pyload

- [CVE-2023-0297](https://insights.sbomify.com/CVE-2023-0297/): Code Injection in pyload/pyload (critical 9.8)
- [CVE-2026-33992](https://insights.sbomify.com/CVE-2026-33992/): pyLoad: Server-Side Request Forgery via Download Link Submission Enables Cloud Metadata Exfiltration (critical 9.3)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44226 is a medium-severity vulnerability in pyload, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44226 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-44226/ (Markdown: https://insights.sbomify.com/CVE-2026-44226/index.md)
```

## Sources

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

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