CVE-2026-41133: pyload · DEPRECATED: Insufficient Session Expiration
Affects pyloadSource GCVE Database
Not known to be exploited · CVSS 8.8 High.
Data as of 12 Nov 2026, 01:32 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 8.8 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Apr 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 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pyload pyload | Affected
| Fixed in– |
AI-suggested
Apply the fix provided in commit e95804fb0d06cbb07d2ba380fc494d9ff89b68c1 to ensure session data is properly invalidated or refreshed when user roles or permissions change. Until patched, users should be advised to log out and log back in after permission changes. No other mitigations are specified.
Description
pyLoad versions up to 0.5.0b3.dev97 have an insufficient session expiration vulnerability where user roles and permissions cached at login remain valid until session expiry or logout. This allows users to retain revoked privileges during an active session, leading to unauthorized privileged actions. A fix has been committed to address this issue.