CVE-2026-23996: FastAPI Api Key Timing Attack Vulnerability

CVE-2026-23996 Overview

CVE-2026-23996 is a timing side-channel vulnerability affecting the FastAPI API Key library, a backend-agnostic library that provides an API key authentication system. The vulnerability exists in the verify_key() method of version 1.1.0 and earlier, where a random delay was only applied on verification failures. This implementation flaw allows an attacker to statistically distinguish valid from invalid API keys by measuring response latencies.

Critical Impact
With enough repeated requests, an adversary could infer whether a key_id corresponds to a valid key, potentially accelerating brute-force or enumeration attacks against protected API endpoints.

Affected Products

FastAPI API Key library versions prior to 1.1.0
Applications using verify_key() for API key authentication

Discovery Timeline

2026-01-21 - CVE CVE-2026-23996 published to NVD
2026-01-21 - Last updated in NVD database

Technical Details for CVE-2026-23996

Vulnerability Analysis

This vulnerability is classified as CWE-208 (Observable Timing Discrepancy), a type of side-channel attack that exploits timing differences in cryptographic operations. The core issue stems from the verify_key() function's asymmetric handling of successful and failed authentication attempts.

When an API key verification fails, the original implementation introduced a random delay to mitigate timing attacks. However, successful verifications did not receive the same treatment. This differential behavior creates an observable timing oracle that attackers can exploit through statistical analysis.

An attacker with network access can submit numerous authentication requests and measure the response times. Over a sufficient sample size, the statistical difference between valid and invalid key responses becomes detectable, allowing the attacker to enumerate valid API keys without triggering traditional rate-limiting mechanisms.

Root Cause

The root cause is an incomplete timing attack mitigation in the verify_key() method. The original implementation only applied random delays to failed authentication attempts, creating a measurable timing difference between success and failure code paths. This constitutes an observable timing discrepancy (CWE-208) that leaks information about the validity of submitted API keys.

Attack Vector

The attack is network-based and requires no privileges or user interaction. An attacker can exploit this vulnerability by:

Sending multiple authentication requests with candidate API keys to the target endpoint
Recording response latencies for each request
Performing statistical analysis on the collected timing data
Identifying keys that produce consistently different response times, indicating valid keys
Using enumerated valid keys for further attacks or unauthorized access

python

 import asyncio
 import os
+import warnings
 from dataclasses import dataclass
 from datetime import datetime
 from random import SystemRandom
 from abc import ABC, abstractmethod
-from typing import Optional, Tuple, List
+from typing import List, Optional, Tuple
 
 from fastapi_api_key.domain.entities import ApiKey
 from fastapi_api_key.domain.errors import KeyNotProvided, KeyNotFound, InvalidKey, ConfigurationError

Source: GitHub Commit Reference

The patch introduces uniform random delay application for all verification outcomes, eliminating the timing correlation between response times and authentication results.

Detection Methods for CVE-2026-23996

Indicators of Compromise

Unusually high volume of authentication requests from single IP addresses or ranges
Sequential or pattern-based API key submission attempts in authentication logs
Abnormal authentication failure rates with consistent timing patterns
Statistical anomalies in request patterns suggesting timing analysis attacks

Detection Strategies

Monitor authentication endpoints for high-frequency request patterns that may indicate timing analysis
Implement alerting for authentication request volumes that exceed normal baseline thresholds
Analyze authentication logs for patterns consistent with enumeration attempts
Deploy network-level monitoring to identify requests with artificially controlled timing intervals

Monitoring Recommendations

Enable detailed logging for all verify_key() function calls including timestamps
Track authentication failure rates per source IP and flag anomalous patterns
Implement request timing analysis to detect potential timing attack reconnaissance
Review application dependencies and verify FastAPI API Key library version is 1.1.0 or later

How to Mitigate CVE-2026-23996

Immediate Actions Required

Upgrade FastAPI API Key library to version 1.1.0 or later immediately
Audit all applications using the verify_key() method for API key authentication
Implement rate limiting on authentication endpoints as a defense-in-depth measure
Review authentication logs for signs of previous exploitation attempts

Patch Information

The vulnerability is addressed in FastAPI API Key version 1.1.0. The patch applies a uniform random delay (from min_delay to max_delay) to all responses regardless of authentication outcome, eliminating the timing correlation. Users should upgrade by updating their dependency to version 1.1.0 or later. For detailed patch information, see the GitHub Security Advisory GHSA-95c6-p277-p87g and the GitHub Release Version 1.1.0.

Workarounds

Add an application-level fixed delay or random jitter to all authentication responses (both success and failure) before applying the official patch
Implement aggressive rate limiting to reduce the feasibility of statistical timing attacks
Deploy a Web Application Firewall (WAF) with rules to detect and block high-frequency authentication probing
Consider implementing CAPTCHA or proof-of-work mechanisms for authentication endpoints

bash

# Configuration example - Upgrade FastAPI API Key
pip install --upgrade fastapi-api-key>=1.1.0

# Verify installed version
pip show fastapi-api-key | grep Version