pyLoad's Session Not Invalidated After Permission Changes
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI pyload-ng
- Affected
- <= 0.5.0b3.dev97
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-fj52-5g4h-gmq8 lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev97
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-fj52-5g4h-gmq8 lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev97
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 2.9 · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:P · score source
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Summary The pyload application does not properly invalidate or modify sessions upon changes made to a user's permissions. Details Whenever an administrator changes the permissions a specific account has, they do not expect that account still being able to access data that their new permissions do not allow. This is not the case for the pyload application, as a user with a valid session can still perform the actions. PoC Take a user with all the permissions, as shown below. We now log in as this user. Let us now take away all the permissions. The logged in session can still be used to access everything in the application. Impact Should permissions be taken away, then the user is expected not to be able to execute the actions belonging to those actions anymore.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-fj52-5g4h-gmq8
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-fj52-5g4h-gmq8
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-fj52-5g4h-gmq8 Advisory: pyLoad's Session Not Invalidated After Permission Changes IDs: GHSA-fj52-5g4h-gmq8 Record: https://patchnext.com/advisories/ghsa-fj52-5g4h-gmq8 (revision 3, source checked 26 Oct 2026, 13:46 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Low (CVSS 2.9) 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-fj52-5g4h-gmq8 (OSV record GHSA-fj52-5g4h-gmq8 lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev97) - Verified: https://github.com/advisories/GHSA-fj52-5g4h-gmq8 (GitHub-reviewed advisory GHSA-fj52-5g4h-gmq8 lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev97) Commands are suggestions: review each one before running it.
Loading voting…