Valid key identification via failure-only response delay
Published Jan 21, 2026 · Updated Jan 21, 2026
Timing side channel in Athroniaeth keyshield before 1.1.0 allows remote attackers to identify valid API key IDs through latency probes. The verify_key method delays exception paths but returns successful verification results without the same randomized wait, exposing an observable timing difference. Exploitation requires repeated measurements against an application that exposes this method; the oracle reveals identifier validity, not the API key secret itself.
Summary
What happened
Timing side channel in Athroniaeth keyshield before 1.1.0 allows remote attackers to identify valid API key IDs through latency probes. The verify_key method delays exception paths but returns successful verification results without the same randomized wait, exposing an observable timing difference. Exploitation requires repeated measurements against an application that exposes this method; the oracle reveals identifier validity, not the API key secret itself.
The record
- CVE
- CVE-2026-23996
- Published
- Jan 21, 2026
- Updated
- Jan 21, 2026
- Vendor
- Athroniaeth
- Product
- keyshield
- Classifications
- CWE-208, T1212
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2026CVE publishedPublication date reported by the CVE source.
- Jan 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo