PatchSiren cyber security CVE debrief
CVE-2026-80202 kimai CVE debrief
Kimai before 2.56.0 does not enforce team-membership checks in TimesheetVoter::voteOnAttribute(). This allows any authenticated user with ROLE_TEAMLEAD to read, modify, and permanently delete timesheets belonging to any user system-wide via the API. Timesheet IDs are sequential integers and trivially enumerable. ROLE_USER accounts are correctly restricted. The issue is characterized by maintainers as matching the documented permission model. Affected product deployments should be verified, and owners assigned for follow-up. Official advisories and CVE records should be reviewed to validate affected scope, severity, and vendor guidance. Compensating controls should be planned for exposed systems while remediation is scheduled and verified.
- Vendor
- kimai
- Product
- Unknown
- CVSS
- CRITICAL 9.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-26
- Original CVE updated
- 2026-09-03
- Advisory published
- 2026-08-26
- Advisory updated
- 2026-09-03
Who should care
Administrators and users of Kimai installations, especially those with ROLE_TEAMLEAD users, should verify and restrict permissions to prevent system-wide timesheet access. This includes reviewing current team membership checks and ensuring that ROLE_TEAMLEAD permissions are appropriately limited to prevent unauthorized access to timesheets across the system. Additionally, implementing compensating controls such as monitoring for suspicious activity can help mitigate potential risks until the update is applied. Users with ROLE_USER accounts are correctly restricted and do not need to take additional action beyond standard security practices.
Technical summary
Kimai before 2.56.0 does not enforce team-membership checks in TimesheetVoter::voteOnAttribute(). This allows any authenticated user with ROLE_TEAMLEAD to read, modify, and permanently delete timesheets belonging to any user system-wide via the API. Timesheet IDs are sequential integers and trivially enumerable. ROLE_USER accounts are correctly restricted. The issue is characterized by maintainers as matching the documented permission model.
Defensive priority
Authenticated users with ROLE_TEAMLEAD can read, modify, and delete timesheets system-wide; verify team membership checks and restrict ROLE_TEAMLEAD permissions.
Recommended defensive actions
- Verify team membership checks in TimesheetVoter::voteOnAttribute()
- Restrict ROLE_TEAMLEAD permissions to prevent system-wide timesheet access
- Implement compensating controls to monitor and limit API access
- Inventory and update Kimai installations to version 2.56.0 or later
- Monitor for suspicious timesheet modifications and deletions
Evidence notes
Kimai before 2.56.0 does not enforce team-membership checks in TimesheetVoter::voteOnAttribute(). Any authenticated user with ROLE_TEAMLEAD can read, modify, and permanently delete timesheets system-wide via the API. Timesheet IDs are sequential integers and trivially enumerable. ROLE_USER accounts are correctly restricted. Evidence is limited to CVE and NVD details.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-80202 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-80202
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-80202 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-80202
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/kimai/kimai/security/advisories/GHSA-9g2q-w3w2-vf7q
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/kimai-before-2.56.0-authorization-bypass-via-timesheetvoter
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.