Auth bypass in Pyload
CVE-2026-123816
pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev101, Api.check_apikey caches successful validation in self._apikey_cache using only the attacker-controlled key_id. After a legitimate key populates the cache, a forged API key with the same key_id reaches the cache-hit path without comparing apikey[-43:] to the stored hash through hmac.compare_digest. Key identifiers are small sequential integers, so an unauthenticated remote attacker can enumerate an active identifier and inherit the cached key owner's permissions during the 300-second cache lifetime. This issue is fixed in version 0.5.0b3.dev101.
Vulnerability class: Broken Authentication
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.1 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Pyload — versions < 0.5.0b3.dev101
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-123816?
- CVE-2026-123816 is a high-severity vulnerability in Pyload, classified under Improper Authentication. CVSS score: 8.1/10. Published 2026-11-09.
- How severe is CVE-2026-123816?
- High severity. CVSS v3 base score is 8.1 out of 10.