CVE-2026-52822
Received Received - Intake

Privilege Escalation in Kimai Time Tracking via Historical Timesheet Access

Publication date: 2026-09-15

Last updated on: 2026-09-15

Assigner: GitHub, Inc.

Description
Kimai is an open-source time tracking application. Prior to 2.58.0, PATCH /api/timesheets/{id}/restart, PATCH /api/timesheets/{id}/duplicate, and the web duplicate workflow can derive a new record from an owned historical timesheet after the user's access to its project or activity has been revoked. TimesheetVoter evaluates the own-timesheet permission before current team access, and its canStart() logic validates object visibility but does not verify the user's current team access to the referenced project and activity. An old entry therefore acts as a persistent capability to create new time records under an unauthorized project and activity, corrupting budgets, statistics, reports, and invoices after an administrative revocation. This issue is fixed in version 2.58.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-15
Last Modified
2026-09-15
Generated
2026-09-15
AI Q&A
2026-09-15
EPSS Evaluated
N/A
NVD
CVE-2026-52822
EUVD
EUVD-2026-78407

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
kimai kimai 2.58.0
kimai kimai to 2.58.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-285 The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Kimai (versions 2.57.0 and earlier) allows users to restart or duplicate old timesheet entries even after their access to the associated project or activity has been revoked. The system checks ownership of historical timesheets before verifying current team access, letting unauthorized users create new time records under revoked projects. This corrupts budgets, statistics, reports, and invoices.

Detection Guidance

Check Kimai version with: grep -r "version" /path/to/kimai/composer.json. If version is <=2.57.0, the system is vulnerable. Review logs for unauthorized timesheet restarts or duplications via API endpoints /api/timesheets/{id}/restart and /api/timesheets/{id}/duplicate.

Impact Analysis

If you use Kimai versions 2.57.0 or earlier, an attacker with past access could log time on projects they no longer have permission to use. This distorts project tracking, financial reports, and invoicing by including unauthorized entries. It undermines administrative access controls and data integrity.

Compliance Impact

This vulnerability could lead to inaccurate financial or time-tracking records, violating compliance requirements for data accuracy and audit trails. For GDPR, it may affect data integrity in time logs. For HIPAA, it risks improper billing or record-keeping. Organizations must update to version 2.58.0 to ensure compliance.

Mitigation Strategies

Update Kimai to version 2.58.0 or newer immediately. Verify all users no longer have access to revoked projects by checking team assignments. Audit timesheets for unauthorized entries created after access revocation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-52822. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart