Quick answers
- Is CVE-2026-84806 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84806 being exploited in the wild.
- How severe is CVE-2026-84806?
- Medium severity, with a CVSS score of 5.4, published 2 September 2026.
- Which products and versions are affected?
- Kimai before 2.63.0.
- Is there a fix for CVE-2026-84806?
- A patch was published on 2026-09-02: Version 2.63.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84806 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-84806?
- 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
Kimai before 2.63.0 contains a business logic / improper authorization vulnerability in team access endpoints. The vulnerable endpoints (POST /api/teams/{id}/customers/{customerId}, POST /api/teams/{id}/projects/{projectId}, POST /api/teams/{id}/activities/{activityId}) check only that the caller has edit permission on the team and view permission on the target entity, but fail to verify edit permission on the entity itself. An authenticated attacker with team edit permissions and read-only access to a customer, project, or activity can send POST requests to these endpoints to add that entity to a team's access control list, thereby granting unauthorized team access. The vulnerability requires authentication and network access to the API endpoints. The fix (version 2.63.0+) replaces the view permission check with a proper edit permission check for all entity types.
Affected products
- Kimai Kimai before 2.63.0
Timeline
- 2026-08-19: disclosed
- 2026-09-02: advisory
- 2026-09-02: patched: Version 2.63.0 released