How severe is GHSA-fj52-5g4h-gmq8?

No CVSS score has been assigned to GHSA-fj52-5g4h-gmq8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fj52-5g4h-gmq8?

GHSA-fj52-5g4h-gmq8 affects the following packages: pyload-ng (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-fj52-5g4h-gmq8?

No patched version of pyload-ng has shipped for GHSA-fj52-5g4h-gmq8 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-fj52-5g4h-gmq8 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pyload-ng, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-fj52-5g4h-gmq8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-fj52-5g4h-gmq8?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fj52-5g4h-gmq8 can be triaged on real exposure rather than presence alone.

Is GHSA-fj52-5g4h-gmq8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-fj52-5g4h-gmq8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-fj52-5g4h-gmq8 published, and has it been updated?

GHSA-fj52-5g4h-gmq8 was published on April 14, 2026 and was last updated on April 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-fj52-5g4h-gmq8 — pyload-ng

Fix: pyload/pyload@e95804f

GHSA-fj52-5g4h-gmq8 is a security vulnerability in pyload-ng. No vendor fix is recorded yet; mitigation options are listed below.

pyLoad's Session Not Invalidated After Permission Changes

Published

Apr 14, 2026

Updated

Apr 14, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Apr 14, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍pyload-ng

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pyload-ng`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pyload-ng, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of pyload-ng has shipped for GHSA-fj52-5g4h-gmq8 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fj52-5g4h-gmq8 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-fj52-5g4h-gmq8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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. ![image](https://user-images.githubusercontent.com/44903767/294956335-0e4da84f-bf9a-42c8-87f1-f5ff35967c

O3 Security · Impact-Aware SCA

Is GHSA-fj52-5g4h-gmq8 in your dependencies?

O3 Security finds GHSA-fj52-5g4h-gmq8 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works