# CVE-2026-28685: Kimai: API invoice endpoint missing customer-level access control (IDOR)

> Team leads can read all invoices regardless of customer assignment due to missing customer-level access control checks.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-v33r-r6h2-8wr7

## What is CVE-2026-28685?

CVE-2026-28685 is a medium-severity missing authorization vulnerability in kimai, published on 6 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Kimai is a web-based multi-user time-tracking application. Prior to version 2.51.0, "GET /api/invoices/{id}" only checks the role-based view_invoice permission but does not verify the requesting user has access to the invoice's customer. Any user with ROLE_TEAMLEAD (which grants view_invoice) can read all invoices in the system, including those belonging to customers assigned to other teams. This issue has been patched in version 2.51.0.

Weakness: CWE-285 (Improper Authorization)

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

2 open source packages ship an affected version, including kimai/kimai. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kimai/kimai` | Packagist | All versions | 2.51.0 |
| `kimai/kimai` | Packagist | All versions | 2.51.0 |

Products: Kimai Kimai.

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

Upgrade kimai/kimai to 2.51.0 or later.

## Is CVE-2026-28685 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28685 exists.

## Other vulnerabilities in kimai

- [CVE-2020-19825](https://insights.sbomify.com/CVE-2020-19825/): Cross-site Scripting in kimai/kimai (critical 9.6)
- [CVE-2023-53957](https://insights.sbomify.com/CVE-2023-53957/): Kimai 1.30.10 SameSite Cookie Vulnerability Session Hijacking (high 8.5)
- [CVE-2021-43515](https://insights.sbomify.com/CVE-2021-43515/): Improper Neutralization of Formula Elements in a CSV File in Kimai 2 (high 7.8)
- [CVE-2023-46245](https://insights.sbomify.com/CVE-2023-46245/): Kimai (Authenticated) SSTI to RCE by Uploading a Malicious Twig File (high 7.2)
- [CVE-2026-23626](https://insights.sbomify.com/CVE-2026-23626/): Kimai Vulnerable to Authenticated Server-Side Template Injection (SSTI) (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28685 is a medium-severity missing authorization vulnerability in kimai, published on 6 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28685 exists.

Affected packages and fixed versions:
- kimai/kimai (Packagist): affected all versions; fixed in 2.51.0
- kimai/kimai (Packagist): affected all versions; fixed in 2.51.0

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-28685/ (Markdown: https://insights.sbomify.com/CVE-2026-28685/index.md)
```

## Sources

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

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