CVE-2026-52827
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
Summary
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 Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| kimai | kimai | < 2.59.0 | affected |
Weaknesses
- CWE-287: CWE-287: Improper Authentication
References
- https://github.com/kimai/kimai/security/advisories/GHSA-v8hx-4vx8-wc96
- https://github.com/kimai/kimai/pull/5957
- https://github.com/kimai/kimai/commit/87c85270a98899e6545108cbb9f41103ec6ea312
- https://github.com/kimai/kimai/releases/tag/2.59.0
- https://www.kimai.org/en/security/ghsa-v8hx-4vx8-wc96
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.