Vulnerability · Published Sep 15, 2026 · Assigned by GitHub_M

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

High 7.1

In plain English

A high-severity improper authentication in kimai from kimai. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.6% (higher than 48% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 4.0)7.1High

Exploit odds (30 days)0.6%top 52.3% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

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.

Affected packages & fixed versions

Ecosystem	Package	Fixed in	Advisory
Packagist	kimai/kimai	2.59.0	GHSA-v8hx-4vx8-wc96

Affected products (as reported)

Vendor	Product	Versions
kimai	kimai	< 2.59.0

Weakness: CWE-287 · Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

References

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