# CVE-2026-84806: Kimai improper authorization in team access endpoints

Source: https://junglewise.ai/threats/cve-2026-84806-kimai-improper-authorization-in-team-access-endpoints  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-02. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

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

Kimai is a time tracking and project management application used by teams to record work hours and manage billable activities. A flaw in its team access control system allows authenticated users with limited permissions to grant their team inappropriate access to customers, projects, or activities they should not be able to modify, potentially exposing sensitive project data and disrupting access control integrity.

Technologies: [Kimai](https://junglewise.ai/threats/technologies/kimai). Vendors: [Kimai](https://junglewise.ai/threats/vendors/kimai).

## 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

## References

- [https://github.com/kimai/kimai/security/advisories/GHSA-gmm9-hfxg-7v29](https://github.com/kimai/kimai/security/advisories/GHSA-gmm9-hfxg-7v29)
- [https://www.vulncheck.com/advisories/kimai-before-2.63.0-authorization-bypass-via-team-access-endpoints](https://www.vulncheck.com/advisories/kimai-before-2.63.0-authorization-bypass-via-team-access-endpoints)

## Related threats

- [Kimai missing authorization check in ExportController export templates](https://junglewise.ai/threats/cve-2026-52828-kimai-missing-authorization-check-in-exportcontroller-export)
- [Kimai 2FA bypass in REST API via session cookie replay](https://junglewise.ai/threats/cve-2026-52827-kimai-2fa-bypass-in-rest-api-via-session-cookie-replay)
- [Kimai improper authorization in rate edit endpoints](https://junglewise.ai/threats/cve-2026-52826-kimai-improper-authorization-in-rate-edit-endpoints)
- [Kimai improper authorization in Team assignment APIs](https://junglewise.ai/threats/cve-2026-52825-kimai-improper-authorization-in-team-assignment-apis)
- [Kimai insecure default APP_SECRET in Docker image](https://junglewise.ai/threats/cve-2026-52824-kimai-insecure-default-app-secret-in-docker-image)