Kimai is an open-source time tracking application. Prior to 2.57.0, GET or POST requests to /en/admin/project/{id}/rate/{rate}, /en/admin/customer/{id}/rate/{rate}, and /en/admin/activity/{id}/rate/{rate} independently resolve the authorized parent identifier and the attacker-selected child rate identifier without confirming that the ProjectRate, CustomerRate, or ActivityRate belongs to that parent. An authenticated user who can edit one parent object can pair it with a rate record from an unauthorized project, customer, or activity and persist changes to billing configuration in kimai2_projects_rates, kimai2_customers_rates, or kimai2_activities_rates. This issue is fixed in version 2.57.0.
CVE-2026-52826
MEDIUMPre-NVD 5.35.3—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% 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).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0
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
- 18%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
September 15, 2026
Advisory Details (4)
Auto-updated Sep 15, 2026🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_release.
generic
Users could edit rates of projects, customers, or activities outside their access – Kimai
https://www.kimai.org/en/security/ghsa-2xgg-2x8h-8xw4github_release Patch Available
2.57.0
Patch available: kimai/kimai 2.57.0
https://github.com/kimai/kimai/releases/tag/2.57.0github_pr Patch Available
Release 2.57
Patch available: kimai/kimai 2.57.0 (PR #5929 merged 2026-05-21)
https://github.com/kimai/kimai/pull/5929github Patch Available🟡 PoC Available
Improper Authorization in Kimai Project, Customer, and Activity Rate Edit Endpoints Allows Cross-Scope Rate Manipulation · Advisory · kimai/kimai · GitHub
https://github.com/kimai/kimai/security/advisories/GHSA-2xgg-2x8h-8xw4Vendor Advisories for CVE-2026-52826(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 (202 versions) | 2.57.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 13:33 UTCEG score recompute
- 2026-09-15 12:53 UTCEG score recompute
- 2026-09-15 11:29 UTCEG score recompute
- 2026-09-15 10:50 UTCEG score recompute▲ 5.30
- 2026-09-15 10:47 UTCMITRE cvelistV5CVSS v3 → 5.3 · CVSS v4 → 5.3
- 2026-08-01 02:49 UTCEG score recompute
- 2026-07-26 11:50 UTCEG score recompute
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-14 00:25 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-52826?
CVE-2026-52826 is a medium vulnerability published on July 14, 2026. Kimai is an open-source time tracking application. Prior to 2.57.0, GET or POST requests to /en/admin/project/{id}/rate/{rate}, /en/admin/customer/{id}/rate/{rate}, and /en/admin/activity/{id}/rate/{rate} independently resolve the authorized parent identifier and the attacker-selected child rate…
When was CVE-2026-52826 disclosed?
CVE-2026-52826 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52826 actively exploited?
CVE-2026-52826 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.3% of all scored CVEs.
What is the CVSS score of CVE-2026-52826?
CVE-2026-52826 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-52826?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52826, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52826
Is Your Infrastructure Affected by CVE-2026-52826?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.