# Kimai has Missing Object-Level Authorization in the Team API

Advisory record · `GHSA-jv9x-w4gm-hwcm`

- **Identifiers:** `GHSA-jv9x-w4gm-hwcm` · `CVE-2026-41498` · `PKSA-hb9p-xyj3-gfyj`
- **State:** Confirmed
- **Severity:** CVSS 3.3 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 24 Apr 2026
- **Updated:** 12 May 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 Apr 2026, 16:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `kimai/kimai` (Packagist): affected `<2.54.0`; fixed in `2.54.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Kimai versions before 2.54.0 have a missing object-level authorization check in the Team API, so any user with the edit_team permission can modify any team, including its members, customers, projects and activities, even if they are not a member or teamlead of that team. In default configuration only administrator roles hold that permission, so the flaw matters mainly when an administrator grants edit_team to a lower-privilege role. Upgrade to Kimai 2.54.0 or later.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 3.3 Low, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0025, the 16th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 8 May 2026, 04:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-41498)
- 31 Oct 2026, 14:25 UTC: First seen by agentprime
- 31 Oct 2026, 14:25 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jv9x-w4gm-hwcm)

## Sources

- [GitHub Advisory Database: GHSA-jv9x-w4gm-hwcm](https://github.com/advisories/GHSA-jv9x-w4gm-hwcm)
- [OSV: GHSA-jv9x-w4gm-hwcm](https://osv.dev/vulnerability/GHSA-jv9x-w4gm-hwcm)
- <https://github.com/kimai/kimai/security/advisories/GHSA-jv9x-w4gm-hwcm>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-41498>
- <https://github.com/kimai/kimai>
- <https://github.com/kimai/kimai/releases/tag/2.54.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jv9x-w4gm-hwcm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jv9x-w4gm-hwcm/>. Everything for agents: <https://agentprime.io/llms.txt>.
