CVE-2026-123813: pyload · DEPRECATED: Insufficient Session Expiration
Affects pyloadSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 0.5.0b3.dev102 soon.
Data as of 9 Nov 2026, 21:19 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 0.5.0b3.dev102
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade pyload to 0.5.0b3.dev102.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pyloadpyload | Affected
| Fixed in
|
AI-suggested
Upgrade pyLoad to version 0.5.0b3.dev102 or later, where the issue is fixed by invalidating existing sessions upon permission or password changes. No additional mitigation is required if the upgrade is applied.
Description
pyLoad versions prior to 0.5.0b3.dev102 have an insufficient session expiration vulnerability. When an administrator changes a user's permissions or password via the API, existing Flask sessions are not invalidated. This allows users to retain revoked privileges or continue using sessions established with old credentials until the session expires. The issue does not affect API-key authentication. The vulnerability is fixed in version 0.5.0b3.dev102.