# CVE-2026-52827: Kimai 2FA bypass in REST API via session cookie replay

Source: https://junglewise.ai/threats/cve-2026-52827-kimai-2fa-bypass-in-rest-api-via-session-cookie-replay  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-15. Updated: 2026-07-14  
License: CC BY 4.0 with a link back

CVE-2026-52827 · Severity: high · CVSS 4 · Published 2026-09-15

Kimai is an open-source time-tracking application used by businesses to manage projects and billing. A security flaw allows an attacker who has stolen a user's password to completely bypass two-factor authentication (2FA) when accessing the system's programming interface (API). This means that even if a user has 2FA enabled to protect their account, an attacker can still access and modify their data using only their password.

Technologies: [Kimai](https://junglewise.ai/threats/technologies/kimai), [kimai/kimai (Packagist)](https://junglewise.ai/threats/technologies/kimai-kimai). Vendors: [Kimai](https://junglewise.ai/threats/vendors/kimai), [Packagist](https://junglewise.ai/threats/vendors/packagist).

## Quick answers

**Is CVE-2026-52827 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-52827 being exploited in the wild.

**How severe is CVE-2026-52827?** High severity, with a CVSS score of 4, published 15 September 2026.

**Which products and versions are affected?** Kimai < 2.59.0; kimai/kimai (Packagist) < 2.59.0, ECOSYSTEM:introduced=0,fixed=2.59.0.

**Is there a fix for CVE-2026-52827?** Yes. kimai/kimai (Packagist): upgrade to 2.59.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-52827 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-52827?** Check whether you run Kimai or kimai/kimai (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- kimai/kimai (Packagist): upgrade to 2.59.0 or later

  ```sh
  composer require kimai/kimai:^2.59.0
  ```


## Technical details

A vulnerability in Kimai's API firewall allows for a full bypass of two-factor authentication (TOTP). The root cause is that the 'KIMAI_SESSION' cookie, which is issued immediately after a successful password verification but before the 2FA step, is incorrectly treated as fully authenticated by the REST API endpoints. The API firewall was configured to accept the 'IS_AUTHENTICATED' role, which is satisfied by the 'TwoFactorToken' generated during the 2FA transition. An attacker with valid user credentials can capture this session cookie and replay it against any '/api/*' endpoint to perform actions as the user without providing the second factor. This has been fixed in version 2.59.0 by requiring the 'IS_AUTHENTICATED_REMEMBERED' role for API access.

## Affected products

- Kimai Kimai < 2.59.0

## Identifiers

- CVE-2026-52827
- GHSA-v8hx-4vx8-wc96

## Timeline

- 2026-06-29: disclosed
- 2026-07-14: advisory: GitHub Advisory published

## References

- [https://api.github.com/users/shafiqaimanx](https://api.github.com/users/shafiqaimanx)
- [https://github.com/shafiqaimanx](https://github.com/shafiqaimanx)
- [https://api.github.com/users/shafiqaimanx/gists%7B/gist_id%7D](https://api.github.com/users/shafiqaimanx/gists%7B/gist_id%7D)
- [https://api.github.com/users/shafiqaimanx/repos](https://api.github.com/users/shafiqaimanx/repos)
- [https://avatars.githubusercontent.com/u/65850328?v=4](https://avatars.githubusercontent.com/u/65850328?v=4)
- [https://api.github.com/users/shafiqaimanx/events%7B/privacy%7D](https://api.github.com/users/shafiqaimanx/events%7B/privacy%7D)

## Related threats

- [Kimai missing authorization check in ExportController export templates](https://junglewise.ai/threats/cve-2026-52828-kimai-missing-authorization-check-in-exportcontroller-export)
- [Kimai improper authorization in rate edit endpoints](https://junglewise.ai/threats/cve-2026-52826-kimai-improper-authorization-in-rate-edit-endpoints)
- [Kimai improper authorization in Team assignment APIs](https://junglewise.ai/threats/cve-2026-52825-kimai-improper-authorization-in-team-assignment-apis)
- [Kimai insecure default APP_SECRET in Docker image](https://junglewise.ai/threats/cve-2026-52824-kimai-insecure-default-app-secret-in-docker-image)
- [Kimai CSRF in Timesheet Stop and Restart API endpoints](https://junglewise.ai/threats/cve-2026-52823-kimai-csrf-in-timesheet-stop-and-restart-api-endpoints)