Quick answers
- Is CVE-2026-84808 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84808 being exploited in the wild.
- How severe is CVE-2026-84808?
- Medium severity, with a CVSS score of 4.3, published 2 September 2026.
- Which products and versions are affected?
- Kimai before 2.65.0.
- Is there a fix for CVE-2026-84808?
- A patch was published on 2026-09-02: Version 2.65.0 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84808 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-84808?
- 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-863) in the GET /api/timesheets endpoint of Kimai's REST API. The TimesheetRepository's addPermissionCriteria() method checked project and customer team membership but failed to enforce activity-team access controls. A user with the view_other_timesheet permission (default for ROLE_TEAMLEAD) can list timesheets that use activities restricted to teams they do not belong to, whereas the single-entity GET /api/timesheets/{id} endpoint correctly enforces these restrictions. The attack requires authentication (view_other_timesheet permission) and network access to the API. The fix adds activity constraint validation to addPermissionCriteria(), patched in version 2.65.0.
Affected products
- Kimai Kimai before 2.65.0
Timeline
- 2026-08-19: disclosed: Security advisory published on GitHub
- 2026-09-02: patched: Version 2.65.0 released with fix