Vulnerability in kimai/kimai (CVE-2026-41498)
Summary
Vulnerability in kimai/kimai (CVE-2026-41498). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.54.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41498 has been found in kimai/kimai.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: upgrade kimai/kimai to 2.54.0 or later.
If unsure, ask your IT team or search "kimai/kimai CVE-2026-41498" on the vendor's site.
CVE-2026-41498 (kimai/kimai) — CWE-862 / CVSS v3 3.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.54.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in kimai/kimai.
Check the vendor advisory for the affected versions of kimai/kimai.
Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.54.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'kimai/kimai' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'kimai/kimai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
kimai/kimaiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade kimai/kimai to 2.54.0ステージング環境で 2.54.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com