CVE-2026-84807

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-09-02. a secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Kimai (kimai/kimai) through 2.65.0 contains a business logic / improper authorization vulnerability in the default team creation endpoints. An authenticated user with project permission-management privileges can create or use a customer, project, or activity whose name matches an existing team; because the endpoints POST /api/customers/{id}/team, POST /api/projects/{id}/team, and POST /api/activities/{id}/team reuse an existing team of the same name and add the current user as teamlead without verifying that the user is authorized to manage that team, the attacker gains unauthorized team-lead (administration) rights over the existing team. Fixed in 2.65.0.

CVSS v3
5.4
EG Score
5.4(high)
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 computed
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

September 2, 2026

Last Modified

September 2, 2026

Advisory Details (2)

Auto-updated Sep 2, 2026
Patch available. Sources: github.
generic

Kimai before 2.65.0 Authentication Bypass via Team Creation | Advisories | VulnCheck

https://www.vulncheck.com/advisories/kimai-before-2.65.0-authentication-bypass-via-team-creation
github Patch Available

Creating a default team could grant team lead rights on an existing team · Advisory · kimai/kimai · GitHub

https://github.com/kimai/kimai/security/advisories/GHSA-hvq2-5gh2-rgvv

Vendor Advisories for CVE-2026-84807(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 49× 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.

  1. 2026-09-20 04:36 UTCEG score recompute
  2. 2026-09-20 04:36 UTCGHSA enrichment
  3. 2026-09-19 02:17 UTCEG score recompute
  4. 2026-09-19 02:17 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-17 23:57 UTCEG score recompute
  7. 2026-09-17 23:57 UTCGHSA enrichment
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-16 21:21 UTCEG score recompute
  10. 2026-09-16 21:21 UTCGHSA enrichment
  11. 2026-09-16 14:09 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 18:21 UTCEG score recompute
  14. 2026-09-15 18:21 UTCGHSA enrichment
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-15 03:12 UTCEPSS rescore
  17. 2026-09-14 15:53 UTCEG score recompute
  18. 2026-09-14 15:53 UTCGHSA enrichment
  19. 2026-09-13 13:33 UTCGHSA enrichment
  20. 2026-09-12 11:13 UTCEG score recompute
  21. 2026-09-12 11:13 UTCGHSA enrichment
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 08:53 UTCEG score recompute
  25. 2026-09-11 08:53 UTCGHSA enrichment
Show 24 more
  1. 2026-09-10 06:33 UTCGHSA enrichment
  2. 2026-09-09 04:13 UTCEG score recompute
  3. 2026-09-09 04:13 UTCGHSA enrichment
  4. 2026-09-08 22:01 UTCEPSS rescore
  5. 2026-09-08 01:51 UTCEG score recompute
  6. 2026-09-08 01:50 UTCGHSA enrichment
  7. 2026-09-06 23:31 UTCEG score recompute
  8. 2026-09-06 23:31 UTCGHSA enrichment
  9. 2026-09-06 13:48 UTCEPSS rescore
  10. 2026-09-05 21:11 UTCEG score recompute
  11. 2026-09-05 21:11 UTCGHSA enrichment
  12. 2026-09-05 15:31 UTCEPSS rescore
  13. 2026-09-04 18:52 UTCEG score recompute
  14. 2026-09-04 18:52 UTCGHSA enrichment
  15. 2026-09-04 05:07 UTCEPSS rescore
  16. 2026-09-03 16:32 UTCGHSA enrichment
  17. 2026-09-02 14:11 UTCGHSA enrichment
  18. 2026-09-02 13:33 UTCEG score recompute
  19. 2026-09-02 13:32 UTCGHSA enrichment
  20. 2026-09-02 12:56 UTCEG score recompute
  21. 2026-09-02 12:56 UTCGHSA enrichment
  22. 2026-09-02 12:26 UTCEG score recompute
  23. 2026-09-02 11:24 UTCEG score recompute
  24. 2026-09-02 11:23 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-84807?
CVE-2026-84807 is a medium vulnerability published on September 2, 2026. Kimai (kimai/kimai) through 2.65.0 contains a business logic / improper authorization vulnerability in the default team creation endpoints. An authenticated user with project permission-management privileges can create or use a customer, project, or activity whose name matches an existing team;…
When was CVE-2026-84807 disclosed?
CVE-2026-84807 was first published in the National Vulnerability Database on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84807 actively exploited?
CVE-2026-84807 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 95.4% of all scored CVEs.
What is the CVSS score of CVE-2026-84807?
CVE-2026-84807 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-84807?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84807, 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

Explore the affected products and dependency analysis for CVE-2026-84807

Explore →

Is Your Infrastructure Affected by CVE-2026-84807?

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

Start Free Scan →Browse All CVEs