Kimai: Two-factor authentication bypass on the Kimai API (CVE-2026-52827) | HOL Guard CVE

High severityCVE-2026-52827GHSA-V8HX-4VX8-WC96

Kimai: Two-factor authentication bypass on the Kimai API

Answer in brief

CVE-2026-52827 records a High severity vulnerability in Kimai: Two-factor authentication bypass on the Kimai API. The current sources do not mark it as known exploited. The current feed maps kimai/kimai (composer), kimai/kimai (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 15, 2026Updated Sep 15, 2026Source checked Sep 15, 2026First seen by HOL Jul 14, 2026Material review Sep 15, 2026

Upstream Advisory

Key facts

Risk: High
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps kimai/kimai (composer), kimai/kimai (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
kimai/kimaicomposer	<2.59.0	2.59.0
kimai/kimaigeneric	< 2.59.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for kimai/kimai, kimai/kimai.
Review the reported fix. Update kimai/kimai to 2.59.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jul 14, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.