Summary
pyLoad: Privilege revocation and password change through the REST API do not invalidate the user's session
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. set_session in webui/app/helpers.py writes role and perms once, and both login_required and the session branch of apikey_auth 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/json_blueprint.py, at the three WebUI form handlers. Api.set_user_permission and Api.change_password in core/api/init.py write to the database and return. Both are exported over /api/ 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 at set_user_permission and noting that it updates the database role and permission only. What that advisory does not do is name /api/set_user_permission as a reachable route, and it does not mention change_password at all, which is the half I think is new.
I ran this against pyload-ng 0.5.0b3.dev101 installed from PyPI, on a real instance with real users. Demoting an admin from role 0 to role 1 with permission 0 by POSTing /api/set_user_permission updated the database immediately. The demoted user's existing session still returned 200 on /api/get_userdir, still loaded /settings, and still wrote reconnect.script through /api/set_config_value, which is the admin-only option CVE-2026-33509 was published for. The identical change through /json/update_users killed that session at once: the same request returned 401 and /settings redirected to the login page.
The password path behaves the same way. After POSTing /api/change_password for a user, their old password was refused at login and the new one accepted, but the session opened under the old password kept working. Through /json/change_password it was dropped. So an owner who rotates a password through the API to evict somebody does not evict them.
One limit worth stating: the API-key branch of apikey_auth reads the user from the database on every request, so key-authenticated callers are not stale. This affects the session branch only.
webui.session_lifetime defaults to 44640 minutes, so a stale session can outlive the revocation by about a month.
I think the invalidation belongs beside the database write in the core API rather than in the blueprint, so that every caller of these operations picks it up. Re-reading role and permission from the database per request would close the whole class, but that is a larger change and I have not measured what it would cost here.
I used AI assistance while investigating this, and every result above was executed by me against the released wheel with the paired control runs shown.
Impact
GHSA-JQ7H-WRVP-3RGX has a CVSS score of 7.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-JQ7H-WRVP-3RGX? GHSA-JQ7H-WRVP-3RGX is a high-severity security vulnerability in pyload-ng (pip), affecting versions <= 0.5.0b3.dev101. No fixed version is listed yet.
- How severe is GHSA-JQ7H-WRVP-3RGX? GHSA-JQ7H-WRVP-3RGX has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of pyload-ng are affected by GHSA-JQ7H-WRVP-3RGX? pyload-ng (pip) versions <= 0.5.0b3.dev101 is affected.
- Is there a fix for GHSA-JQ7H-WRVP-3RGX? No fixed version is listed for GHSA-JQ7H-WRVP-3RGX yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is GHSA-JQ7H-WRVP-3RGX exploitable, and should I be worried? Whether GHSA-JQ7H-WRVP-3RGX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-JQ7H-WRVP-3RGX is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.