CVE-2026-23996

描述

### 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

如何修補 CVE-2026-23996

要修補 CVE-2026-23996,請將受影響套件升級到下列已修補版本。

• —升級至 1.1.0 或更新版本

CVE-2026-23996 正在被利用嗎?

低 — EPSS 為 0.1%,目前沒有觀察到大規模利用活動。

受影響套件(1)

• from 0, < 1.1.0

CVSS 分數