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.
CVE-2026-52822
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 24(Track)EG Risk 24/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 29%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
September 15, 2026
Advisory Details (5)
Auto-updated Sep 15, 2026Users could keep logging time on projects after their access was revoked – Kimai
https://www.kimai.org/en/security/ghsa-c6w6-57jj-62vh2.58.0
Patch available: kimai/kimai 2.58.0
https://github.com/kimai/kimai/releases/tag/2.58.0commit 31a8f887a5cd (kimai/kimai)
Patch available: kimai/kimai 2.58.0 (contains commit 31a8f887a5cd)
https://github.com/kimai/kimai/commit/31a8f887a5cda517db7b4320a7ad997c87d08601Release 2.58
Patch available: kimai/kimai 2.58.0 (PR #5952 merged 2026-05-25)
https://github.com/kimai/kimai/pull/5952Improper Authorization in Kimai Timesheet Restart and Duplicate Allows New Timesheets After Project Access Revocation · Advisory · kimai/kimai · GitHub
https://github.com/kimai/kimai/security/advisories/GHSA-c6w6-57jj-62vhVendor Advisories for CVE-2026-52822(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| kimai/kimai | 0.1 ... 2.9.0 (203 versions) | 2.58.0 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 04:59 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 14:37 UTCEG score recompute
- 2026-09-15 13:58 UTCEG score recompute
- 2026-09-15 11:29 UTCEG score recompute
- 2026-09-15 10:54 UTCEG score recompute▲ 5.30
- 2026-09-15 10:53 UTCMITRE cvelistV5CVSS v3 → 5.3 · CVSS v4 → 5.3
- 2026-08-01 11:45 UTCEG score recompute
- 2026-07-26 11:50 UTCEG score recompute
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-14 00:09 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-285 · CWE-862
Frequently asked(5)
What is CVE-2026-52822?
When was CVE-2026-52822 disclosed?
Is CVE-2026-52822 actively exploited?
What is the CVSS score of CVE-2026-52822?
How do I remediate CVE-2026-52822?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52822
Is Your Infrastructure Affected by CVE-2026-52822?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.