Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- High severity, with a CVSS score of 8.1, published 9 October 2026.
- Which products and versions are affected?
- pyload-ng (PyPI) < 0.5.0b3.dev101.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Disable or restrict API key access until patched, limit API usage to trusted networks via firewall rules, or rotate API keys frequently to reduce cache reuse window impact. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run pyload-ng (PyPI) or 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
Disable or restrict API key access until patched, limit API usage to trusted networks via firewall rules, or rotate API keys frequently to reduce cache reuse window impact.
Technical details
The vulnerability exists in the API key cache implementation in pyLoad's check_apikey() function, which keys the cache solely on key_id (a small sequential integer easily enumerated) rather than the full API key secret. On a cache hit within the 300-second TTL, the code returns success after only checking expiration, never verifying the supplied secret using hmac.compare_digest(). An attacker can construct a forged API key with a guessed key_id and gain full privileges of the associated user if that key_id was recently authenticated.
Affected products
- pyLoad
Timeline
- 2026-10-09: disclosed