CVE-2026-52825 Kimai has Improper Authorization in Team Member and Team Activity Assignment APIs Which Allows Expansion of Team Scope Beyond Authorized Visibility
Team leads can add unauthorized users or activities to teams via API, bypassing visibility restrictions and affecting downstream authorization logic.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-52825?
CVE-2026-52825 is a medium-severity missing authorization vulnerability in kimai, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Kimai is an open-source time tracking application. Prior to 2.58.0, POST /api/teams/{id}/members/{userId} and POST /api/teams/{id}/activities/{activityId} verify that a teamlead may edit the Team but do not verify access_user for the referenced User or view access for the referenced Activity. A teamlead can add users or activities outside the teamlead's manageable scope to an editable team, bypassing the narrower choices enforced by TeamEditForm and UserRepository::getQueryBuilderForFormType(). The resulting relationships can be trusted by RolePermissionManager::checkTeamAccessActivity() and other team-based authorization, visibility, reporting, and workflow logic. This issue is fixed in version 2.58.0.
Which versions are affected by CVE-2026-52825?
2 open source packages ship an affected version, including kimai/kimai.
| Package | Affected | Fixed in |
|---|---|---|
kimai/kimai Packagist | All versions | 2.58.0 |
kimai/kimai Packagist | All versions | 2.58.0 |
How do I fix CVE-2026-52825?
Upgrade kimai/kimai to 2.58.0 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-52825 being exploited?
There is no known exploitation of CVE-2026-52825 in the wild and no public exploit code.
Sources
Also known as GHSA-xv4r-4885-gwpg.