Is CVE-2026-52825 exploited in the wild?

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

How severe is CVE-2026-52825?

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

Which products and versions are affected?

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

Is there a fix for CVE-2026-52825?

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

How is CVE-2026-52825 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-52825?

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-52825: Kimai improper authorization in Team assignment APIs

Q: Which products and versions are affected?

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

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

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

Q: How is CVE-2026-52825 attacked?

It is attacked over the network, in a web application.

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

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-52825 · Severity: medium · CVSS 4 · Published 2026-09-15

Kimai, an open-source time-tracking application, contains a flaw where team leads can bypass intended restrictions to manage users and activities outside their authorized scope. By using specific backend programming interfaces, a team lead can add unauthorized users or business activities to their team, even if those items are hidden in the standard user interface. This could lead to unauthorized access to sensitive project data, incorrect reporting, and a breakdown of the security boundaries between different teams.

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

Quick answers

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

Technical details

An improper authorization vulnerability exists in Kimai's Team Controller API. While the frontend correctly restricts visible users and activities based on a Teamlead's scope, the backend endpoints `POST /api/teams/{id}/members/{userId}` and `POST /api/teams/{id}/activities/{activityId}` only verify if the caller has 'edit' permissions for the team. They fail to validate if the referenced User or Activity objects are within the caller's management domain. An authenticated attacker with Teamlead privileges can exploit this to attach arbitrary users or activities to their team. This can lead to privilege escalation as downstream authorization logic often trusts these team-object relationships for access control decisions. The issue is fixed in version 2.58.0 by adding explicit permission checks for the referenced entities.

Affected products

Kimai kimai/kimai <= 2.57.0

Identifiers

CVE-2026-52825
GHSA-xv4r-4885-gwpg

Timeline

2026-06-11: disclosed
2026-07-14: advisory: GitHub Advisory published
2026-07-14: patched: Version 2.58.0 released

References

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