Skip to main content
← Vulnerabilities

pyLoad: Privilege revocation and password change through the REST API do not invalidate the user's session

Affects pyload-ng up to and including 0.5.0b3.dev101 for web session logins; API-key authentication is not affected. No vendor rating is given. Fixed in 0.5.0b3.dev102.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.5.0b3.dev102
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Affected pyload-ng versions up to and including 0.5.0b3.dev101 Applies to web session authentication; API-key authentication is not affected Stale session stays valid for the configured session lifetime (default 44640 minutes)

Published
Last modified
26/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

pyLoad, a Python-based download manager, fails to end existing login sessions when an administrator changes a user's permissions or password through its REST API. A user with low-privilege login access can, remotely, keep using revoked privileges or an old-password session until the session expires.

Read the original description

pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev102, pyLoad does not invalidate existing Flask sessions when an administrator changes a user's permissions or password through /api/set_user_permission or /api/change_password. Api.set_user_permission and Api.change_password update the database, but session authorization continues to use role and permission values copied at login by set_session in webui/app/helpers.py. A user can therefore retain revoked privileges or continue using a session established with an old password for the configured session lifetime. API-key authentication is not affected because that path rereads user data from the database. This issue is fixed in version 0.5.0b3.dev102.

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects PyPI packages
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 76 if added to CISA KEV
  • Would score about 71 if CISA's SSVC rates exploitation active
  • Would score about 33 if CISA's SSVC rates it automatable

Impact

  • Widely used

    pyload-ng has 1.2k weekly downloads.Source: pypistats.org

    1 packages depend on pyload-ng.Source: deps.dev

What to do

  • Check whether your setup matches what the bug needs.

    Affected pyload-ng versions up to and including 0.5.0b3.dev101 Applies to web session authentication; API-key authentication is not affected Stale session stays valid for the configured session lifetime (default 44640 minutes)
  • Upgrade to a fixed version: 0.5.0b3.dev102.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • pyload pyload

    fixed in 0.5.0b3.dev102

  • through 0.5.0b3.dev101

    No fix released.

Evidence 2

  1. Advisory
  2. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-123813

Is CVE-2026-123813 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

After a user's privileges are revoked or the user's password is changed, an existing web session stays valid. That user keeps admin-level access through the session, including writing admin-only settings such as reconnect.script, until the session expires (default 44640 minutes).Source: github.com

Which versions are affected by CVE-2026-123813?

pyload: before 0.5.0b3.dev102. pyload-ng (PyPI): through 0.5.0b3.dev101.Source: cve.now feed data

Am I affected, and how do I check?

Versions of pyload-ng up to and including 0.5.0b3.dev101 are affected, and only for web session authentication; API-key authentication is not affected. To check an installation, compare its pyload-ng version with 0.5.0b3.dev101 and confirm whether the web interface logs in with sessions rather than API keys.Source: github.com

How do I fix CVE-2026-123813?

Upgrade to 0.5.0b3.dev102 or later, which contains the fix. The facts list no workaround.Source: github.com