CVE-2026-123816: pyload · Improper Authentication
Affects pyloadSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 0.5.0b3.dev101 soon.
Data as of 9 Nov 2026, 21:34 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 8.1 |
|---|
- Patch
- Available – fixed in 0.5.0b3.dev101
CVSS:3.1/AV:N/AC:H/PR:N/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.dev101.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pyloadpyload | Affected
| Fixed in
|
AI-suggested
Upgrade pyLoad to version 0.5.0b3.dev101 or later, where the improper authentication caching issue is fixed. No other mitigation is required as the vendor has provided an official fix.
Description
pyLoad versions prior to 0.5.0b3.dev101 contain an improper authentication vulnerability in the API key validation caching mechanism. The system caches successful API key validations keyed only by the attacker-controlled key_id, which are small sequential integers. This allows an unauthenticated remote attacker to enumerate active key identifiers and reuse cached permissions for 300 seconds without proper key verification. The issue is fixed in version 0.5.0b3.dev101.