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.
CVE-2026-80195
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.
- 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.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 computedSeverity54% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 26, 2026
Advisory Details (2)
Auto-updated Aug 25, 2026Kimai 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-apiKimai 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-pp46Vendor 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 14× in last 7d / 14× 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-08-30 01:31 UTCEG score recompute
- 2026-08-30 01:31 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 00:02 UTCEG score recompute
- 2026-08-29 00:01 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 18:51 UTCEG score recompute
- 2026-08-27 18:50 UTCGHSA enrichment
- 2026-08-26 17:21 UTCEG score recompute
- 2026-08-26 16:22 UTCEG score recompute
- 2026-08-26 15:56 UTCEG score recompute
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 23:25 UTCEG score recompute
- 2026-08-25 23:24 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-80195?
When was CVE-2026-80195 disclosed?
Is CVE-2026-80195 actively exploited?
What is the CVSS score of CVE-2026-80195?
How do I remediate CVE-2026-80195?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-80195
Is Your Infrastructure Affected by CVE-2026-80195?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.