pyLoad has Stale Session Privilege After Role/Permission Change (Privilege Revocation Bypass)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-41133: 0.33% estimated exploitation activity in the next 30 days; percentile 25.65 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary pyLoad caches 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. Details The WebUI auth flow stores authorization state in session: - src/pyload/webui/app/helpers.py:187-200 - setsession(...) writes: - "role": userinfo["role"] - "perms": userinfo["permission"] Authorization checks later trust cached session values: - src/pyload/webui/app/helpers.py:134-151 - parsepermissions(...) reads session.get("role") / session.get("perms") - src/pyload/webui/app/helpers.py:225-230 - isauthenticated(...) only verifies authenticated and api.userexists(user) (existence), not fresh role/permission -…

Published by the source

14 Apr 2026, 23:38 UTC

Last modified by the source

13 Jul 2026, 16:42 UTC

Source last checked

26 Oct 2026, 13:40 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-66hx-chf7-3332

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-66hx-chf7-3332

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41133

Advisory: pyLoad has Stale Session Privilege After Role/Permission Change (Privilege Revocation Bypass)
IDs: CVE-2026-41133, GHSA-66hx-chf7-3332
Record: https://patchnext.com/advisories/cve-2026-41133 (revision 2, source checked 26 Oct 2026, 13:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI pyload-ng: affected <= 0.5.0b3.dev97

## Suggested inspection (read-only)
- `python -m pip show pyload-ng`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pyload-ng.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-66hx-chf7-3332 (OSV record GHSA-66hx-chf7-3332 lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev97)
- Verified: https://github.com/advisories/GHSA-66hx-chf7-3332 (GitHub-reviewed advisory GHSA-66hx-chf7-3332 lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev97)

Commands are suggestions: review each one before running it.