← Back
CVE-2026-44298
medium
CVSS 4.1
Path Traversal in kimai/kimai (CVE-2026-44298)
Summary
path traversal in kimai/kimai (CVE-2026-44298). Risk of unauthorized operations or information disclosure. Exploitable via ``ROLE_SYSTE_ADMIN``. Mitigation: upgrade to `2.56` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44298** has been found in kimai/kimai.
Attackers can target a specific entry point like ``ROLE_SYSTE_ADMIN`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.1/10.
What to do: upgrade kimai/kimai to **2.56** or later.
If unsure, ask your IT team or search "kimai/kimai CVE-2026-44298" on the vendor's site.
CVE-2026-44298 (kimai/kimai) — CWE-22 / CVSS v3 4.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `ROLE_SYSTE_ADMIN` / `upload_invoice_template` / `associated_files` / `file_get_contents`
Patched: `2.56` — 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.
❓ What is the problem
**Path traversal** (CWE-22) exists in kimai/kimai. Attackers reach the vulnerable code path via ``ROLE_SYSTE_ADMIN`` without authentication.
📍 Affected scope
kimai/kimai — . Attack surface: `ROLE_SYSTE_ADMIN` / `upload_invoice_template` / `associated_files` / `file_get_contents`.
🔥 Severity
Severity: Medium (CVSS 4.1/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.56**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade kimai/kimai to 2.56ステージング環境で 2.56 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
kimai/kimai
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.56"}]}]