High severity · published Sep 15, 2026
CVE-2026-52827
Kimai: Two-factor authentication bypass on the Kimai API
7.1
CVSS
0.6%
EPSS
No
On KEV
Description
Kimai is an open-source time tracking application. Prior to 2.59.0, the KIMAI_SESSION cookie issued after password verification but before TOTP completion is accepted by every /api route because config/packages/security.yaml protects the API with IS_AUTHENTICATED and App\API\Authentication\ApiRequestMatcher routes an existing session through the main firewall. A Scheb TwoFactorToken satisfies that access rule, and App\Voter\ApiVoter grants API access to its User, allowing an attacker with a valid account password to use authenticated REST API operations without entering the second factor even though web routes remain blocked. This issue is fixed in version 2.59.0.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.6% · higher than 47% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
KI
kimai · kimai
< 2.59.0 · source: vendor
Affected product
KI
kimai
kimai
More from kimai
9.6
CVE-2020-19825
Cross Site Scripting (XSS) vulnerability in kevinpapst kimai2 1.30.0 in /src/Twig/Runtime/MarkdownExtension.php, allows attackers to gain escalated privileges
9.1
CVE-2026-52824
Kimai: Default APP_SECRET in Docker Image Enables Cookie Forgery and Account Takeover
8.8
CVE-2026-80202
Kimai before 2.56.0 Authorization Bypass via TimesheetVoter
8.8
CVE-2026-80193
Kimai before 2.62.0 Authorization Bypass via QuickEntry
8.8
CVE-2023-53957
Kimai 1.30.10 SameSite Cookie Vulnerability Session Hijacking