CVE-2026-52819

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
6.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Kimai is an open-source time tracking application. Prior to 2.57.0, the GET /api/timesheets list endpoint accepts user and users[] target identifiers from a caller with view_other_timesheet but does not apply access_user or verify that a ROLE_TEAMLEAD requester leads a team containing each target user. TimesheetController::cgetAction() adds the resolved users directly to the query while project and customer filtering still permits records on unscoped projects or projects sharing ordinary team membership, allowing a teamlead to retrieve another user's descriptions, timing data, tags, rate, and internalRate even though GET /api/timesheets/{id} would deny access through TimesheetVoter. This issue is fixed in version 2.57.0.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100

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 computed (value × EchelonGraph’s weight)
Severity63% × 45%
The EG Score, 6.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 13, 2026

Last Modified

September 23, 2026

Advisory Details (4)

Auto-updated Sep 15, 2026
Patch available. Sources: github, github_pr, github_release.
Web page

Team leads could read other users' timesheets through the API – Kimai

https://www.kimai.org/en/security/ghsa-4m8q-55qv-9pwp
GitHub release Patch Available

2.57.0

Patch available: kimai/kimai 2.57.0

https://github.com/kimai/kimai/releases/tag/2.57.0
GitHub pull request Patch Available

Release 2.57

Patch available: kimai/kimai 2.57.0 (PR #5929 merged 2026-05-21)

https://github.com/kimai/kimai/pull/5929
GitHub advisoryMentions a patch (unverified)

Teamlead authorization bypass in GET /api/timesheets allows reading other users' timesheet records without being teamlead of the target · Advisory · kimai/kimai · GitHub

https://github.com/kimai/kimai/security/advisories/GHSA-4m8q-55qv-9pwp

Vendor Advisories for CVE-2026-52819(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)
PackageVulnerable rangeFix by version rangeDependents
kimai/kimai0.1 ... 2.9.0 (202 versions)
  • every version up to 2.57.0: fixed in 2.57.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-10-12 15:58 UTCEG score recompute
  4. 2026-10-11 19:41 UTCEG score recompute
  5. 2026-10-11 16:56 UTCEG score recompute
  6. 2026-10-11 14:19 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-01 13:51 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-09-28 09:27 UTCEG score recompute
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Show 17 more
  1. 2026-09-23 19:06 UTCEG score recompute
  2. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-09-23 04:16 UTCEG score recompute
  4. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-09-18 05:00 UTCEG score recompute
  7. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-09-15 16:35 UTCEG score recompute
  10. 2026-09-15 15:25 UTCEG score recompute
  11. 2026-09-15 11:29 UTCEG score recompute
  12. 2026-09-15 10:51 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
  13. 2026-09-15 10:47 UTCMITRE cvelistV5CVSS v3 → 6.3 · CVSS v4 → 6.3
  14. 2026-08-01 08:15 UTCEG score recompute
  15. 2026-07-26 11:50 UTCEG score recompute
  16. 2026-07-23 03:19 UTCEG score recompute
  17. 2026-07-14 00:09 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-52819?
CVE-2026-52819 is a medium-severity vulnerability; its CVE record was published on July 13, 2026. Kimai is an open-source time tracking application. Prior to 2.57.0, the GET /api/timesheets list endpoint accepts user and users[] target identifiers from a caller with viewothertimesheet but does not apply accessuser or verify that a ROLETEAMLEAD requester leads a team containing each target user.…
When was the CVE record for CVE-2026-52819 published?
The CVE record for CVE-2026-52819 was published on July 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 23, 2026; the record at its source may have been updated since.
Is CVE-2026-52819 actively exploited?
CVE-2026-52819 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52819?
CVE-2026-52819 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-52819?
A fix for CVE-2026-52819 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52819 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52819

Explore →

Is Your Infrastructure Affected by CVE-2026-52819?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.