# CVE-2026-41133: pyLoad has Stale Session Privilege After Role/Permission Change (Privilege Revocation Bypass)

> Logged-in users retain revoked privileges until session expiry due to cached role data, allowing unauthorized privileged actions in pyLoad.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 21 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-66hx-chf7-3332, PYSEC-2026-2990

## What is CVE-2026-41133?

CVE-2026-41133 is a high-severity missing authorization vulnerability in pyload, published on 21 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. Versions up to and including 0.5.0b3.dev97 cache `role` and `permission` in the session at login and continues to authorize requests using these cached values, even after an admin changes the user's role/permissions in the database. As a result, an already logged-in user can keep old (revoked) privileges until logout/session expiry, enabling continued privileged actions. This is a core authorization/session-consistency issue and is not resolved by toggling an optional security feature. Commit e95804fb0d06cbb07d2ba380fc494d9ff89b68c1 contains a fix for the issue.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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

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

Products: Pyload Pyload.

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

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

## Is CVE-2026-41133 being exploited?

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

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

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

## Sources

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

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