CVE-2026-80199

Kimai before 2.54.0 Username Enumeration via Timing Oracle

Published Aug 25, 2026 CVSS 4.0 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
Kimai before 2.54.0 contains a timing oracle vulnerability in TokenAuthenticator that allows unauthenticated attackers to enumerate valid usernames via X-AUTH-USER header. Attackers can measure response time differences when the password hasher runs only for existing users, enabling username enumeration with no login throttling protection.

Analysis

AI-generated

Technical impact

Kimai prior to version 2.54.0 contains a timing oracle in the TokenAuthenticator that leaks the existence of usernames. By sending requests with an X-AUTH-USER header and measuring response durations, an unauthenticated attacker can distinguish whether the password hash routine was executed for a valid user. The exploit has no built‑in login throttling, allowing rapid enumeration. This flaw is classified as a CWE‑208 information‑leak weakness, leading to partial disclosure of directory or user naming information, which may assist in further credential‑guessing or social‑engineering attacks.

Affected Systems

The vulnerability affects installations of Kimai Kimai running any version earlier than 2.54.0. The exact version list is not provided beyond the major version boundary, so all releases before 2.54.0 are potentially vulnerable.

Risk and Exploitability

The CVSS score of 6.3 marks this as a medium‑severity flaw. Because EPSS is not available, the likelihood of exploitation is unclear, but the lack of throttling increases risk. The vulnerability is not listed in the CISA KEV catalog. Attackers may access publicly reachable API endpoints, so the primary attack vector is over HTTP using the X-AUTH-USER header; the exact service endpoint is not specified but is likely an authentication guard. No specific prerequisites beyond connectivity to the service are mentioned.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Kimai to version 2.54.0 or later to eliminate the timing oracle in TokenAuthenticator
  • If upgrading is delayed, disable or remove the X‑AUTH‑USER header processing in the authentication flow, or refactor the component to perform the password hash uniformly regardless of username validity
  • Implement request rate limiting or login throttling on the authentication endpoint to reduce the effectiveness of timing measurements
  • Remove or hide timing differences in the response by ensuring identical processing times for both valid and invalid usernames

Generated by OpenCVE AI on August 26, 2026 at 01:33 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Kimai before 2.54.0 contains a timing oracle vulnerability in TokenAuthenticator that allows unauthenticated attackers to enumerate valid usernames via X-AUTH-USER header. Attackers can measure response time differences when the password hasher runs only for existing users, enabling username enumeration with no login throttling protection.
Title Kimai before 2.54.0 Username Enumeration via Timing Oracle
First Time appeared Kimai
Kimai kimai
Weaknesses CWE-208
CPEs cpe:2.3:a:kimai:kimai:*:*:*:*:*:*:*:*
Vendors & Products Kimai
Kimai kimai
References
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N'}

cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-208

    Observable Timing Discrepancy

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 8, 2026, 3:25 PM
Reserved
Aug 25, 2026, 11:14 PM
Status
Deferred
Published
Aug 26, 2026, 5:18 AM
Modified
Oct 8, 2026, 4:17 PM