Is CVE-2026-84804 exploited in the wild?

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

How severe is CVE-2026-84804?

Medium severity, with a CVSS score of 5.4, published 2 September 2026.

Is there a fix for CVE-2026-84804?

A patch was published on 2026-09-02: Version 2.65.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-84804 attacked?

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

Am I affected by CVE-2026-84804?

Check whether you run Kimai 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-84804: Kimai authorization bypass in team activity API

CVE-2026-84804 · Severity: medium · CVSS 5.4 · Published 2026-09-02

Kimai is an open-source time-tracking and project management application. Before version 2.65.0, the API endpoints that remove team access to activities, projects, and customers fail to properly validate that the user has permission to manage those resources. An authenticated user with basic team-editing privileges can remove team access without the additional authorization check that should be required, allowing unauthorized access revocation.

Technologies: Kimai. Vendors: Kimai.

Quick answers

Is CVE-2026-84804 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-84804 being exploited in the wild.
How severe is CVE-2026-84804?: Medium severity, with a CVSS score of 5.4, published 2 September 2026.
Which products and versions are affected?: Kimai before 2.65.0.
Is there a fix for CVE-2026-84804?: A patch was published on 2026-09-02: Version 2.65.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-84804 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-84804?: Check whether you run Kimai 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.

Technical details

The vulnerability is an authorization bypass (CWE-862: Missing Authorization) in Kimai's REST API team management endpoints. The DELETE routes at /api/teams/{id}/activities/{activityId}, /api/teams/{id}/projects/{projectId}, and /api/teams/{id}/customers/{customerId} only check if the caller has edit_team permission on the target team, but fail to validate the permissions_activity (or equivalent) permission on the target activity, project, or customer—a check that is correctly enforced when granting access. An authenticated API user with edit_team permission can therefore revoke team access to resources they are not authorized to manage. The fix, released in version 2.65.0, adds the missing permission checks to all three revoke endpoints, ensuring that removing access requires the same authorization level as granting it.

Affected products

Kimai Kimai before 2.65.0

Timeline

2026-08-19: disclosed
2026-09-02: advisory
2026-09-02: patched: Version 2.65.0 released

References

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