# CVE-2026-123813: pyLoad: Privilege revocation and password change through the REST API do not invalidate the user's session


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-jq7h-wrvp-3rgx

## What is CVE-2026-123813?

CVE-2026-123813 is a high-severity vulnerability in pyload, published on 9 Nov 2026. 

### Official 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.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2026-123813?

1 open source package ship an affected version, including pyload-ng.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyload-ng` | PyPI | All versions to 0.5.0b3.dev101 | None |

## How do I fix CVE-2026-123813?

No fix has been published for CVE-2026-123813 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123813 being exploited?

There is no known exploitation of CVE-2026-123813 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123813 and fix it if it is affected.

What it is: CVE-2026-123813 is a high-severity vulnerability in pyload, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123813 in the wild and no public exploit code.

Affected packages and fixed versions:
- pyload-ng (PyPI): affected all versions up to 0.5.0b3.dev101; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123813/ (Markdown: https://insights.sbomify.com/CVE-2026-123813/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123813
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123813
- OSV: https://osv.dev/vulnerability/CVE-2026-123813

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123813/
Summaries are generated and may contain mistakes; the official description above is the record.