pyLoad: Api.set_user_permission never invalidates the target's session

Exploitation

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

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary An admin who revokes or downgrades a non-admin user's permissions through pyLoad's own documented /api/<func RPC surface — e.g. POST /api/setuserpermission (or its legacy alias /api/setUserPermission) — updates the target's database row but never invalidates that user's existing Flask cookie session. The demoted user keeps their pre-revocation role/permission bits on every subsequent WebUI page load and every subsequent /api/<func call made with that cookie, for up to the default sessionlifetime of ~31 days, or until they voluntarily log out. No action by the demoted user is required beyond already being logged in at the time of revocation. Details The vulnerable method, verbatim, at src/pyload/core/api/init.py:1652-1656: It carries no @permission(...) decorator and its body never calls clearallusersessions or any other session-invalidation routine. The only call site in the entire codebase that pairs a permission/role change with clearallusersessions is the WebUI's…

Published by the source

9 Oct 2026, 17:09 UTC

Last modified by the source

9 Oct 2026, 17:09 UTC

Source last checked

26 Oct 2026, 13:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-889w-m37p-88m5

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

# Patch Next advisory brief: GHSA-889w-m37p-88m5

Advisory: pyLoad: Api.set_user_permission never invalidates the target's session
IDs: GHSA-889w-m37p-88m5
Record: https://patchnext.com/advisories/ghsa-889w-m37p-88m5 (revision 1, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
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.dev98, <= 0.5.0b3.dev101

## 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://github.com/advisories/GHSA-889w-m37p-88m5 (GitHub-reviewed advisory GHSA-889w-m37p-88m5 lists affected ranges: PyPI pyload-ng >=0.5.0b3.dev98 <=0.5.0b3.dev101)

Commands are suggestions: review each one before running it.