# CVE-2026-52827

## Summary

- **CVE ID:** CVE-2026-52827
- **Severity:** HIGH
- **CVSS Score:** 7.1 (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)
- **CWE:** CWE-287
- **Published:** Sep 15, 2026
- **Last Modified:** Sep 16, 2026

## 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 — kimai (< 2.59.0)

## References

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

## Exploitation Prediction (EPSS)

- **EPSS Score:** 0.43%
- **EPSS Percentile:** 36.5

---
_Exported from OnDuty AI Vulnerability Intelligence on 2026-09-18._