CVE-2026-52827 Kimai: Two-factor authentication bypass on the Kimai API
Attackers with valid passwords can bypass two-factor authentication to access the Kimai REST API without providing the second factor.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-52827?
CVE-2026-52827 is a high-severity authentication bypass vulnerability in kimai, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-287
Which versions are affected by CVE-2026-52827?
2 open source packages ship an affected version, including kimai/kimai.
| Package | Affected | Fixed in |
|---|---|---|
kimai/kimai Packagist | All versions | 2.59.0 |
kimai/kimai Packagist | All versions | 2.59.0 |
How do I fix CVE-2026-52827?
Upgrade kimai/kimai to 2.59.0 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-52827 being exploited?
There is no known exploitation of CVE-2026-52827 in the wild and no public exploit code.
Sources
Also known as GHSA-v8hx-4vx8-wc96.