CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HCVE-2026-123813 pyLoad: Privilege revocation and password change through the REST API do not invalidate the user's session
High (7.5) in pyload pyload. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
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.
Severity
- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 18th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- OWASP Top 10
- A07:2025 Authentication Failures
- Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Not in the NVD yet
- Record from
- the CVE List, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123813 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123813?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123813?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123813 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-123813)
HTML:
<a href="https://cve.bz/cve/CVE-2026-123813"><img src="https://cve.bz/cve/badge/CVE-2026-123813.svg" alt="CVE-2026-123813"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| pyload | < 0.5.0b3.dev102 |
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-jq7h-wrvp-3rgx | PyPI | pyload-ng | <=0.5.0b3.dev101 | no fix published |