CVE-2026-80195

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

Score 5.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-26. A secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.4Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists kimai versions before 2.63.0 as affected, and kimai versions 2.63.0 as unaffected. No release containing a fix is confirmed on record.

Kimai before 2.63.0 contains a business logic / improper authorization vulnerability in the team update API endpoint (PATCH /api/teams/{id}), which removes all existing team members before validating the submitted replacement member list. An authenticated teamlead (or other user) with permission to edit a team can submit a malformed members payload; although Kimai returns a validation error, the existing membership rows have already been deleted. This bypasses the dedicated member-removal endpoint's protection against removing teamleaders and can leave a team with no members or teamleaders, disrupting team-based access control.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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)
Severity54% × 45%
The EG Score, 5.4 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

August 25, 2026

Last Modified

September 3, 2026

Advisory Details (2)

Auto-updated Aug 25, 2026
No fix on record yet. Sources: github.
Web page

Kimai before 2.63.0 Team Membership Removal via API | Advisories | VulnCheck

https://www.vulncheck.com/advisories/kimai-before-2.63.0-team-membership-removal-via-api
GitHub advisoryMentions a patch (unverified)

Kimai API Team Update Endpoint Removes Team Memberships Before Validating Replacement Members · Advisory · kimai/kimai · GitHub

https://github.com/kimai/kimai/security/advisories/GHSA-6rxf-4hh9-pp46

Vendor Advisories for CVE-2026-80195(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 17× in last 7d / 75× 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.

Showing the most recent 98 of 127 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 29 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  3. 2026-10-12 14:57 UTCEG score recompute
  4. 2026-10-11 19:21 UTCEG score recompute
  5. 2026-10-11 16:37 UTCEG score recompute
  6. 2026-10-11 13:56 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  9. 2026-10-10 10:00 UTCEG score recompute
  10. 2026-10-10 10:00 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  12. 2026-10-09 06:18 UTCEG score recompute
  13. 2026-10-09 06:18 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-10-08 04:48 UTCEG score recompute
  16. 2026-10-08 04:48 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  18. 2026-10-07 03:19 UTCEG score recompute
  19. 2026-10-07 03:19 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-10-06 01:50 UTCEG score recompute
  22. 2026-10-06 01:50 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  23. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  24. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-10-04 19:44 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
Show 73 more
  1. 2026-10-03 16:16 UTCEG score recompute
  2. 2026-10-03 16:16 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  3. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  4. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  5. 2026-10-02 09:18 UTCEG score recompute
  6. 2026-10-02 09:18 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  7. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  8. 2026-10-01 07:49 UTCEG score recompute
  9. 2026-10-01 07:49 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  10. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  11. 2026-09-30 06:20 UTCEG score recompute
  12. 2026-09-30 06:20 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  13. 2026-09-29 00:32 UTCEG score recompute
  14. 2026-09-29 00:32 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  15. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  16. 2026-09-27 22:59 UTCEG score recompute
  17. 2026-09-27 22:59 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  18. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  19. 2026-09-26 21:29 UTCEG score recompute
  20. 2026-09-26 21:29 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  21. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  22. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  23. 2026-09-25 00:18 UTCEG score recompute
  24. 2026-09-25 00:18 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  25. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  26. 2026-09-23 22:10 UTCEG score recompute
  27. 2026-09-23 22:10 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  28. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  29. 2026-09-22 20:41 UTCEG score recompute
  30. 2026-09-22 20:41 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  31. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  32. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  33. 2026-09-21 19:12 UTCEG score recompute
  34. 2026-09-21 19:12 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  35. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  36. 2026-09-20 17:43 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  37. 2026-09-19 16:05 UTCEG score recompute
  38. 2026-09-19 16:05 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  39. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  40. 2026-09-18 14:36 UTCEG score recompute
  41. 2026-09-18 14:36 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  42. 2026-09-17 13:07 UTCEG score recompute
  43. 2026-09-17 13:07 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  44. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  45. 2026-09-16 11:28 UTCEG score recompute
  46. 2026-09-16 11:28 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  47. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  48. 2026-09-15 09:52 UTCEG score recompute
  49. 2026-09-15 09:52 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  50. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  51. 2026-09-14 08:22 UTCEG score recompute
  52. 2026-09-14 08:22 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  53. 2026-09-13 06:53 UTCEG score recompute
  54. 2026-09-13 06:53 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  55. 2026-09-12 05:24 UTCEG score recompute
  56. 2026-09-12 05:24 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  57. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  58. 2026-09-11 03:54 UTCEG score recompute
  59. 2026-09-11 03:54 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  60. 2026-09-10 02:25 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  61. 2026-09-09 00:55 UTCEG score recompute
  62. 2026-09-09 00:55 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  63. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  64. 2026-09-07 11:45 UTCEG score recompute
  65. 2026-09-07 11:45 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  66. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  67. 2026-09-06 10:14 UTCEG score recompute
  68. 2026-09-06 10:14 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  69. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  70. 2026-09-05 08:38 UTCEG score recompute
  71. 2026-09-05 08:38 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4
  72. 2026-09-04 07:08 UTCEG score recompute
  73. 2026-09-04 07:08 UTCGHSA enrichmentGHSA-fcv9-h6ph-8mrc · GitHub severity HIGH · GitHub CVSS 5.4

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-80195?
CVE-2026-80195 is a medium-severity vulnerability; its CVE record was published on August 25, 2026. Kimai before 2.63.0 contains a business logic / improper authorization vulnerability in the team update API endpoint (PATCH /api/teams/{id}), which removes all existing team members before validating the submitted replacement member list. An authenticated teamlead (or other user) with permission to…
When was CVE-2026-80195 made public?
CVE-2026-80195 was made public on August 5, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 25, 2026. EchelonGraph's copy of the record carries a last-modified date of September 3, 2026; the record at its source may have been updated since.
Is CVE-2026-80195 actively exploited?
CVE-2026-80195 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80195?
CVE-2026-80195 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-80195?
No fix for CVE-2026-80195 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists kimai versions before 2.63.0 as affected, and kimai versions 2.63.0 as unaffected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-80195 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-80195?

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

Book a Demo →Browse All CVEs