# CVE-2026-84807: Kimai before 2.65.0 Authentication Bypass via Team Creation

> An authenticated user can gain unauthorized team-lead administration rights by creating entities with names matching existing teams.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/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:** 2 Sep 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-hvq2-5gh2-rgvv, GHSA-p3c7-g2jr-3m35

## What is CVE-2026-84807?

CVE-2026-84807 is a medium-severity vulnerability in kimai, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Kimai (kimai/kimai) before 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.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-84807 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84807 is a medium-severity vulnerability in kimai, published on 2 Sep 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-84807 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-84807/ (Markdown: https://insights.sbomify.com/CVE-2026-84807/index.md)
```

## Sources

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

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