Security readout for executives and security teams
Plain-English summary
This is a low-severity timing leak in Athroniaeth fastapi-api-key. Failed API key checks took a different amount of time than successful checks, which could let an attacker statistically test whether a key identifier is valid. It does not directly expose keys or grant access, but it can make enumeration or brute-force efforts more efficient.
Executive priority
Treat as a routine security update unless the affected authentication endpoint is internet-facing, high-value, or lacks rate limiting. The business risk is indirect: it can help attackers validate targets for later attacks. Prioritize normal patch cycles and verify exposed services first.
Technical view
CVE-2026-23996 is a CWE-208 timing side-channel in verify_key(). The reported issue is that random delay was applied only to failures, creating measurable latency differences between valid and invalid API key checks. Sources list fastapi-api-key versions before 1.1.0 as affected and describe 1.1.0 as applying uniform delay to all outcomes.
Likely exposure
Exposure is limited to applications using Athroniaeth fastapi-api-key and relying on verify_key() for API key authentication in affected versions. Network exposure matters because repeated requests are needed to collect timing data. Applications with strict rate limits and noisy latency conditions are less practical targets.
Exploitation context
No CISA KEV listing or cited evidence of active exploitation is provided. Exploitation requires repeated measurements and statistical analysis, reflected by CVSS high attack complexity. The main impact is confidentiality: learning whether a key_id is valid, which may support later enumeration or brute-force activity.
Researcher notes
The bundle contains a wording inconsistency: it says version 1.1.0 has the issue, but also says users should upgrade to 1.1.0 and lists versions before 1.1.0 as affected. This assessment follows the affected-version and fix statements. Validate against the GitHub advisory before closing remediation.
Mitigation direction
- Upgrade fastapi-api-key to version 1.1.0 per the advisory and release notes.
- Before upgrading, add uniform delay or jitter to all authentication responses.
- Use rate limiting to reduce repeated timing measurements.
- Review vendor guidance for any additional workarounds or implementation notes.
Validation and detection
- Inventory applications using Athroniaeth fastapi-api-key.
- Confirm installed package versions are 1.1.0 or later.
- Identify code paths that call verify_key() for authentication.
- Check authentication endpoints for rate limiting and uniform response timing.
- Review dependency lockfiles, container images, and deployed environments.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-208: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-23996 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N2.21.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.7LowVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Athroniaeth/fastapi-api-key/security/advisories/GHSA-95c6-p277-p87gCVE reference · x_refsource_CONFIRM
- https://github.com/Athroniaeth/fastapi-api-key/commit/310b2c5c77305f38c63c0b917539a0344071dfd8CVE reference · x_refsource_MISC
- https://github.com/Athroniaeth/fastapi-api-key/releases/tag/1.1.0CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Observable Timing Discrepancy
Observable Timing Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
