# CVE-2026-84808: Kimai before 2.65.0 Authorization Bypass via API Timesheet

> Attackers with view permissions can access restricted team timesheets via the API, bypassing data isolation controls in Kimai.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/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:** 2 Sep 2026
- **Also known as:** GHSA-c4jr-h3rc-c3hg, GHSA-c6j4-35fc-x3hw

## What is CVE-2026-84808?

CVE-2026-84808 is a medium-severity missing authorization 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 versions before 2.65.0 contain an authorization bypass vulnerability in the REST API timesheet collection endpoint that fails to enforce activity-team access controls. Users with view_other_timesheet permission can list timesheets using activities restricted to teams they do not belong to, bypassing intended data isolation.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-84808 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84808 is a medium-severity missing authorization 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-84808 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-84808/ (Markdown: https://insights.sbomify.com/CVE-2026-84808/index.md)
```

## Sources

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

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