Quick answers
- Is CVE-2026-123816 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123816 being exploited in the wild.
- How severe is CVE-2026-123816?
- High severity, with a CVSS score of 8.1, published 9 November 2026.
- Which products and versions are affected?
- pyLoad 0.5.0b3 and prior.
- Is there a fix for CVE-2026-123816?
- Yes: fixed in 0.5.0b3.dev101. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123816 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-123816?
- Check whether you run pyLoad at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.5.0b3.dev101
Technical details
The Api.check_apikey() function caches successful validations using only the attacker-controlled key_id, without storing the API key hash required to verify the secret. On cache hits within the 300-second TTL, the secret (apikey[-43:]) is never compared against a stored hash using hmac.compare_digest(), only the expiration time is checked. An unauthenticated remote attacker can enumerate small sequential key identifiers and forge a matching API key to achieve authentication bypass.
Affected products
- pyLoad pyLoad 0.5.0b3 and prior
Timeline
- 2026-08-01: disclosed
- 2026-11-09: advisory