CVE-2026-52827
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.
Scoring
- Severity
- HIGH
- CVSS base score
- 7.1
- CVSS 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
- EPSS probability
- 0.43%
- CWE
- CWE-287
- Published
- 2026-09-15
- Last modified
- 2026-09-16
Affected products
- kimai kimai
Weakness type
Related vulnerabilities
- CVE-2026-82329 — Potential authentication bypass leading to administrative access in Artifactory
- CVE-2026-85595 — Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth
- CVE-2026-42018 — Anonymous user token generation exposure in JFrog Artifactory
- CVE-2026-68569 — Apache Tomcat: Principal lookup can fail open in some cases
- CVE-2026-19977 — EFM ipTIME A3004T Session Validation httpcon_check_session_url improper authentication
- CVE-2026-59500 — Priority - CWE-287: Improper Authentication
- CVE-2026-82695 — Tenda AC18 Telnet telnet missing authentication
- CVE-2026-82694 — Tenda AC1206 Web UI ate R7WebsSecurityHandler missing authentication