# CVE-2026-40071: pyLoad WebUI JSON permission mismatch lets ADD/DELETE users invoke MODIFY-only actions

> Authenticated low-privileged users can bypass permission checks to modify download packages and links via WebUI JSON endpoints.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 9 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-rfgh-63mg-8pwm, PYSEC-2026-2997

## What is CVE-2026-40071?

CVE-2026-40071 is a medium-severity missing authorization vulnerability in pyload, published on 9 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. Prior to 0.5.0b3.dev97, the /json/package_order, /json/link_order, and /json/abort_link WebUI JSON endpoints enforce weaker permissions than the core API methods they invoke. This allows authenticated low-privileged users to execute MODIFY operations that should be denied by pyLoad's own permission model. This vulnerability is fixed in 0.5.0b3.dev97.

Weakness: CWE-863 (Incorrect Authorization)

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

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

Products: Pyload Pyload.

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

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

## Is CVE-2026-40071 being exploited?

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

What it is: CVE-2026-40071 is a medium-severity missing authorization vulnerability in pyload, published on 9 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-40071 exists.

Affected packages and fixed versions:
- pyload-ng (PyPI): affected all versions up to 0.5.0b3; no fix listed
- pyload-ng (PyPI): affected all versions; fixed in 0.5.0b3.dev97
- pyload-ng (PyPI): affected all versions; 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-40071/ (Markdown: https://insights.sbomify.com/CVE-2026-40071/index.md)
```

## Sources

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

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