# CVE-2026-29778: pyLoad: Arbitrary File Write via Path Traversal in edit_package()

> Attackers can write arbitrary files via path traversal in pyLoad's edit_package function due to insufficient input sanitization.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L`)
- **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:** 7 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-6px9-j4qr-xfjw, PYSEC-2026-121

## What is CVE-2026-29778?

CVE-2026-29778 is a high-severity path traversal vulnerability in pyload, published on 7 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. From version 0.5.0b3.dev13 to 0.5.0b3.dev96, the edit_package() function implements insufficient sanitization for the pack_folder parameter. The current protection relies on a single-pass string replacement of "../", which can be bypassed using crafted recursive traversal sequences. This issue has been patched in version 0.5.0b3.dev97.

Weakness: CWE-23 (Relative Path Traversal)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyload-ng` | PyPI | From 0.5.0b3.dev13 | 0.5.0b3.dev97 |
| `pyload-ng` | PyPI | From 0.5.0b3.dev13 | 0.5.0b3.dev97 |
| `pyload-ng` | PyPI | From 0.5.0b3.dev13 | 0.5.0b3.dev97 |

Products: Pyload-Ng Project Pyload-Ng.

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

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

## Is CVE-2026-29778 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29778 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-29778 and fix it if it is affected.

What it is: CVE-2026-29778 is a high-severity path traversal vulnerability in pyload, published on 7 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-29778 exists.

Affected packages and fixed versions:
- pyload-ng (PyPI): affected from 0.5.0b3.dev13; fixed in 0.5.0b3.dev97
- pyload-ng (PyPI): affected from 0.5.0b3.dev13; fixed in 0.5.0b3.dev97
- pyload-ng (PyPI): affected from 0.5.0b3.dev13; fixed in 0.5.0b3.dev97

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

## Sources

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

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