Quick answers
- Is CVE-2026-80195 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-80195 being exploited in the wild.
- How severe is CVE-2026-80195?
- Medium severity, with a CVSS score of 5.4, published 26 August 2026.
- Which products and versions are affected?
- Kimai before 2.63.0.
- Is there a fix for CVE-2026-80195?
- A patch was published on 2026-08-26: Fixed in version 2.63.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-80195 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-80195?
- 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 a business logic flaw in the PATCH /api/teams/{id} API endpoint. The endpoint deletes all existing team members from the database before validating the replacement member list; if validation fails, the deletion is not rolled back. An authenticated user with team-edit permissions can exploit this by sending a malformed members payload, causing Kimai to validate the request, reject it, but keep the deleted membership rows. This bypasses the dedicated DELETE /api/teams/{id}/members/{userId} endpoint, which explicitly prevents teamlead removal. The attack requires authentication and team-edit permissions. The vulnerability affects Kimai versions before 2.63.0; patched versions validate the new member list before making database changes.
Affected products
- Kimai Kimai before 2.63.0
Timeline
- 2026-08-05: disclosed
- 2026-08-26: advisory
- 2026-08-26: patched: Fixed in version 2.63.0