# CVE-2026-41498: Kimai: Team API Missing Object-Level Authorization

> Attackers with edit_team permission can modify any team due to missing object-level authorization checks in the Kimai time tracking application.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2026
- **Updated:** 8 May 2026
- **Also known as:** GHSA-jv9x-w4gm-hwcm

## What is CVE-2026-41498?

CVE-2026-41498 is a low-severity missing authorization vulnerability in kimai, published on 8 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Kimai is an open-source time tracking application. Prior to version 2.54.0, the Team API endpoints use #[IsGranted('edit_team')] instead of #[IsGranted('edit', 'team')], causing Symfony TeamVoter to abstain from voting. This removes entity-level ownership checks on team operations, allowing any user with the edit_team permission to modify any team, not just teams they are authorized to manage. This issue has been patched in version 2.54.0.

Weakness: CWE-862 (Missing Authorization)

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

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.54.0 |
| `kimai/kimai` | Packagist | All versions | 2.54.0 |

Products: Kimai Kimai.

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

Upgrade kimai/kimai to 2.54.0 or later.

## Is CVE-2026-41498 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41498 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-41498 and fix it if it is affected.

What it is: CVE-2026-41498 is a low-severity missing authorization vulnerability in kimai, published on 8 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41498 exists.

Affected packages and fixed versions:
- kimai/kimai (Packagist): affected all versions; fixed in 2.54.0
- kimai/kimai (Packagist): affected all versions; fixed in 2.54.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-41498/ (Markdown: https://insights.sbomify.com/CVE-2026-41498/index.md)
```

## Sources

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

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