CVE-2026-123816: high-severity vulnerability in pyload
pyLoad: Authentication bypass in API key validation (check_apikey cache)
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.1epss 0.4%
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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
pyload · pyloadRelated CVEs — pyload
In the same product, most dangerous first.
CVE-2024-21644HIGHpyLoad unauthenticated flask configuration leakageEPSS 42.4%CVE-2024-21645MEDIUMpyLoad Log InjectionEPSS 24.7%CVE-2025-54802CRITICALpyLoad CNL Blueprint is vulnerable to Path Traversal through `dlc_path` leading to Remote Code Execution (RCE)EPSS 1.4%CVE-2024-32880CRITICALpyLoad allows upload to arbitrary folder lead to RCEEPSS 1.4%CVE-2025-53890CRITICALpyLoad vulnerable to remote code execution through js2py onCaptchaResultEPSS 1.3%CVE-2024-22416CRITICALCross-Site Request Forgery on any API call in pyLoad may lead to admin privilege escalationEPSS 0.9%