pyLoad: Privilege revocation and password change through the REST API do not invalidate the user'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.

An admin who revokes a user's privileges through the REST API does not actually revoke them, because the session carrying those privileges is never invalidated. pyLoad authorizes each request from values copied into the Flask session at login. setsession in webui/app/helpers.py writes role and perms once, and both loginrequired and the session branch of apikeyauth read them back from the session rather than from the database. The fix for GHSA-66hx-chf7-3332 handled this by deleting the user's session files, but the call was added only in webui/app/blueprints/jsonblueprint.py, at the three WebUI form handlers. Api.setuserpermission and Api.changepassword in core/api/init.py write to the database and return. Both are exported over /api/<func and both appear in the OpenAPI spec the project serves at /api, so the documented administration interface takes the unpatched route. I should concede an overlap up front. GHSA-66hx-chf7-3332 does name the core method in its own Details, pointing…

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-jq7h-wrvp-3rgx

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

# Patch Next advisory brief: GHSA-jq7h-wrvp-3rgx

Advisory: pyLoad: Privilege revocation and password change through the REST API do not invalidate the user's session
IDs: GHSA-jq7h-wrvp-3rgx
Record: https://patchnext.com/advisories/ghsa-jq7h-wrvp-3rgx (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.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-jq7h-wrvp-3rgx (GitHub-reviewed advisory GHSA-jq7h-wrvp-3rgx lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev101)

Commands are suggestions: review each one before running it.