Advisory

GHSA-95c6-p277-p87g

Also known as: CVE-2026-23996, PYSEC-2026-1358

Summary

FastAPI Api Key has a timing side-channel in verify_key that allows statistical key validity detection

Details

Impact
Timing side-channel vulnerability in verify_key(). The method applied a random delay only on verification failures, allowing an attacker to statistically distinguish valid from invalid API keys by measuring response latencies. With enough repeated requests, an adversary could infer whether a key_id corresponds to a valid key, potentially accelerating brute-force or enumeration attacks.

Affected: all users relying on verify_key() for API key authentication prior to the fix.

Patches
Yes. Users should upgrade to version 1.1.0 (or the version containing this fix). The patch applies a uniform random delay (min_delay to max_delay) to all responses regardless of outcome, eliminating the timing correlation.

Workarounds

  • Add an application-level fixed delay or random jitter to all authentication responses (success and failure) before the fix is applied.
  • Use rate limiting to reduce the feasibility of statistical timing attacks.

References

  • CWE-208: Observable Timing Discrepancy
  • Commit: 87b27640f77c5ef86c46311b6b5a7e2887e35b77
  • OWASP: https://owasp.org/www-community/attacks/Timing_attack

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-01-21 22:27 UTC
Modified
2026-07-07 17:57 UTC

Affected packages and fixes

fastapi-api-key

PyPI · All systems

Affected

  • introduced 0, fixed 1.1.0 (ecosystem)

Fixed versions

1.1.0

Fix

  • Fixed version 1.1.0
    pip install --upgrade fastapi-api-key==1.1.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences