# CVE-2026-80195: Kimai before 2.63.0 Team Membership Removal via API

> An authenticated user can delete all team members via a malformed API request, bypassing protections and disrupting team-based access control.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-6rxf-4hh9-pp46, GHSA-fcv9-h6ph-8mrc

## What is CVE-2026-80195?

CVE-2026-80195 is a high-severity vulnerability in kimai, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-841 (Improper Enforcement of Behavioral Workflow)

## Which versions are affected by CVE-2026-80195?


## How do I fix CVE-2026-80195?

No fix has been published for CVE-2026-80195 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-80195 being exploited?

There is no known exploitation of CVE-2026-80195 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80195 and fix it if it is affected.

What it is: CVE-2026-80195 is a high-severity vulnerability in kimai, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80195 in the wild and no public exploit code.

Affected product: kimai. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80195/ (Markdown: https://insights.sbomify.com/CVE-2026-80195/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80195
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80195
- OSV: https://osv.dev/vulnerability/CVE-2026-80195

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80195/
Summaries are generated and may contain mistakes; the official description above is the record.