pyload-ng: getUserData/get_userdata exposed at Perms.ANY allow any authenticated account to brute-force the administrator password

Exploitation

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

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary Api.getUserData (legacy) and Api.getuserdata are declared with @permission(Perms.ANY) and are reachable at /api/getUserData and /api/getuserdata. Because Perms.ANY == 0 and pyLoad's permission check is a bitmask AND, that gate is a no-op: every authenticated account passes, including one holding zero permission bits. Both methods are thin wrappers around checkauth(), which the maintainers deliberately restricted to administrators by omitting @permission (no entry in permmap, so isauthorized() returns False for non-admins). The wrappers undo that protection. An attacker holding the lowest-privileged account in the system therefore has a clean binary oracle on the administrator password, with no account lockout anywhere in the codebase, and with the 100 req/min rate limiter bypassable by rotating X-Forwarded-For. Affected code src/pyload/core/api/init.py:1446 and :1464 Root cause src/pyload/core/api/init.py:57 src/pyload/core/api/init.py:108 For requiredperms == 0 this…

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-68w4-83fh-f2w8

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

# Patch Next advisory brief: GHSA-68w4-83fh-f2w8

Advisory: pyload-ng: getUserData/get_userdata exposed at Perms.ANY allow any authenticated account to brute-force the administrator password
IDs: GHSA-68w4-83fh-f2w8
Record: https://patchnext.com/advisories/ghsa-68w4-83fh-f2w8 (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 8.1)
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.dev1, <= 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-68w4-83fh-f2w8 (GitHub-reviewed advisory GHSA-68w4-83fh-f2w8 lists affected ranges: PyPI pyload-ng >=0.5.0b3.dev1 <=0.5.0b3.dev101)

Commands are suggestions: review each one before running it.