What’s Vulnerable › Vulnerabilities

CVE-2026-52827: Kimai: Two-factor authentication bypass on the Kimai API

• Severity: high (CVSS 7.1 v4.0)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.6% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-09-15 · updated 2026-09-30
• Weakness: CWE-287

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.

Affected products

• kimai: before 2.59.0

References

• https://github.com/kimai/kimai/commit/87c85270a98899e6545108cbb9f41103ec6ea312
• https://github.com/kimai/kimai/pull/5957
• https://github.com/kimai/kimai/releases/tag/2.59.0
• https://github.com/kimai/kimai/security/advisories/GHSA-v8hx-4vx8-wc96
• https://www.kimai.org/en/security/ghsa-v8hx-4vx8-wc96

Get alerted when CVE-2026-52827 or the next vulnerability affects your stack