CVE-2026-52827

published 15 Sep 2026 · updated 16 Sep 2026

Kimai: Two-factor authentication bypass on the Kimai API

7.1HighCVSS 7.1EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
kimai<2.59.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-52827 severity on Zeptric[![CVE-2026-52827](https://zeptric.io/badge/cve/CVE-2026-52827.svg)](https://zeptric.io/cve/CVE-2026-52827)