GHSA-jq7h-wrvp-3rgx: pyLoad Privilege Revocation And Password Change Vulnerability

HIGH
CVSS 7.5
CWE-613
Published
Advisory Summary

GHSA-jq7h-wrvp-3rgx is a HIGH (CVSS 7.5) privilege revocation and password change vulnerability (CWE-613: Insufficient Session Expiration) affecting pyLoad libraries in the PyPI ecosystem. The issue involves privilege revocation and password change through the rest api do not invalidate the user's session. Remediation is available in the latest vendor maintenance releases.

GHSA-jq7h-wrvp-3rgx at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-jq7h-wrvp-3rgx
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-613: Insufficient Session Expiration
Affected Product pyLoad
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix GHSA-jq7h-wrvp-3rgx

To remediate this vulnerability, upgrade all affected pyLoad dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

pyload-ng fixed: Latest secure release
pip install pyload-ng>=Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show pyload-ng

How to Check if You Are Affected

To determine whether your Python environment is affected by GHSA-jq7h-wrvp-3rgx, inspect your installed packages using pip:

pip show pyload-ng

Analyze the terminal output to locate any version of pyLoad in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The pip show pyload-ng command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-613: Insufficient Session Expiration, where according to wasc, "insufficient session expiration is when a web site permits an attacker to reuse old session credentials or session ids for authorization.". In pyLoad, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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/<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 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.

GHSA-jq7h-wrvp-3rgx Affected pyLoad Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
pyload-ng
PyPI
≤ 0.5.0b3.dev101

References

Frequently Asked Questions

What is GHSA-jq7h-wrvp-3rgx?
GHSA-jq7h-wrvp-3rgx is a security vulnerability in pyLoad involving Privilege revocation and password change through the REST API do not invalidate the user's session under CWE-613: Insufficient Session Expiration.
Which pyLoad versions are affected?
Affected versions include releases prior to current release patches across affected packages: pyload-ng.
What version fixes GHSA-jq7h-wrvp-3rgx?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is pyload-ng affected?
Yes, pyload-ng is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of GHSA-jq7h-wrvp-3rgx?
GHSA-jq7h-wrvp-3rgx has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with GHSA-jq7h-wrvp-3rgx?
GHSA-jq7h-wrvp-3rgx is classified under CWE-613: Insufficient Session Expiration (According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization.").
How can I check PyPI dependencies for GHSA-jq7h-wrvp-3rgx?
Run the dependency tree command: 'pip show pyload-ng'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jq7h-wrvp-3rgx",
  "modified" : "2026-10-09T17:09:10Z",
  "published" : "2026-10-09T17:09:09Z",
  "aliases" : [ ],
  "summary" : "pyLoad: Privilege revocation and password change through the REST API do not invalidate the user's session",
  "details" : "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.\n\npyLoad 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/<func> and both appear in the OpenAPI spec the project serves at /api, so the documented administration interface takes the unpatched route.\n\nI 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.\n\nI 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.\n\nThe 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.\n\nOne 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.\n\nwebui.session_lifetime defaults to 44640 minutes, so a stale session can outlive the revocation by about a month.\n\nI 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.\n\nI used AI assistance while investigating this, and every result above was executed by me against the released wheel with the paired control runs shown.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "pyload-ng"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.5.0b3.dev101"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/pyload/pyload/security/advisories/GHSA-jq7h-wrvp-3rgx"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pyload/pyload/commit/3e726ba271a6b1015e3a0ea6dc7e46a8f71a62ad"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/pyload/pyload"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-613" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-09T17:09:09Z",
    "nvd_published_at" : null
  }
}