Is CVE-2026-52819 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-52819 being exploited in the wild.

How severe is CVE-2026-52819?

Medium severity, with a CVSS score of 4, published 15 September 2026.

Which products and versions are affected?

Kimai <= 2.56.0; kimai/kimai (Packagist) <= 2.56.0, ECOSYSTEM:introduced=0,fixed=2.57.0.

Is there a fix for CVE-2026-52819?

Yes. kimai/kimai (Packagist): upgrade to 2.57.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-52819 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-52819?

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.

CVE-2026-52819: Kimai authorization bypass in GET /api/timesheets API

Q: Which products and versions are affected?

Kimai <= 2.56.0; kimai/kimai (Packagist) <= 2.56.0, ECOSYSTEM:introduced=0,fixed=2.57.0.

Q: Is there a fix for CVE-2026-52819?

Yes. kimai/kimai (Packagist): upgrade to 2.57.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-52819 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-52819?

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.

CVE-2026-52819 · Severity: medium · CVSS 4 · Published 2026-09-15

Kimai, a popular open-source time-tracking application, contains a security flaw that allows users with 'Teamlead' roles to view the timesheets of any other user in the system. This bypasses intended privacy controls, potentially exposing sensitive activity logs and financial billing rates for employees outside of the teamlead's authorized scope. An exploit could lead to the unauthorized disclosure of personal activity data and corporate financial information.

Technologies: Kimai, kimai/kimai (Packagist). Vendors: Kimai, Packagist.

Quick answers

Is CVE-2026-52819 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-52819 being exploited in the wild.
How severe is CVE-2026-52819?: Medium severity, with a CVSS score of 4, published 15 September 2026.
Which products and versions are affected?: Kimai <= 2.56.0; kimai/kimai (Packagist) <= 2.56.0, ECOSYSTEM:introduced=0,fixed=2.57.0.
Is there a fix for CVE-2026-52819?: Yes. kimai/kimai (Packagist): upgrade to 2.57.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-52819 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-52819?: 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.57.0 or later
```
composer require kimai/kimai:^2.57.0
```

Technical details

An authorization mismatch exists between the per-record voter and the collection endpoint in Kimai's API. While the `GET /api/timesheets/{id}` endpoint correctly enforces teamlead-of-target checks via `TimesheetVoter`, the list endpoint `GET /api/timesheets` only checks for the global `view_other_timesheet` permission, which is granted to all teamleads. An attacker with `ROLE_TEAMLEAD` can use the `user` or `users[]` query parameters to retrieve records for any user, provided the records are on projects without team scoping or projects where the attacker is a member. This leaks sensitive fields including `rate`, `internalRate`, and activity descriptions. The issue is fixed in version 2.57.0 by introducing the `access_user` permission check in `TimesheetController::cgetAction()`.

Affected products

Kimai Kimai <= 2.56.0

Identifiers

CVE-2026-52819
GHSA-4m8q-55qv-9pwp

Timeline

2026-06-11: disclosed: Initial disclosure to vendor
2026-07-13: advisory: GitHub Advisory published
2026-07-13: patched: Fix released in version 2.57.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.