Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

Summary

Users with the role System-Admin (ROLE_SYSTE_ADMIN) and the permission upload_invoice_template can upload PDF invoice templates, which can call pdfContext.setOption('associated_files', ...) inside the sandboxed Twig render.

This is forwarded to mPDF's SetAssociatedFiles(), whose writer calls file_get_contents($entry['path']) during PDF output and embeds the bytes as a FlateDecode stream in the PDF. Any file readable by the PHP worker is returned to the attacker inside the rendered invoice.

Root cause

  1. src/Twig/SecurityPolicy/StrictPolicy.php:123-128 explicitly whitelists PdfContext::setOption():

    if ($obj instanceof PdfContext) {
    if ($lcm !== 'setoption') { throw ...; }
    return;
}

  2. src/Pdf/MPdfConverter.php keeps associated_files in the pass-through allowlist:

    $allowed = ['mode','format','default_font_size','default_font', ... , 'associated_files','additional_xmp_rdf'];

    and then forwards it to mPDF:

    if (array_key_exists('associated_files', $options) && is_array($options['associated_files'])) {
    $associatedFiles = $options['associated_files'];
    unset($options['associated_files']);
}
...
$mpdf->SetAssociatedFiles($associatedFiles);

  3. mPDF 8.3.1 MetadataWriter::writeAssociatedFiles() calls file_get_contents, which respects PHP stream wrappers:

    if (isset($file['path'])) {
    $fileContent = @file_get_contents($file['p…

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-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.

📍 Affected scope

Check the vendor advisory for the affected versions of 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'kimai/kimai' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で kimai/kimai を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade kimai/kimai to 2.56

    ステージング環境で 2.56 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer kimai/kimai
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.56"}]}]
Packagist kimai/kimai
[{"type":"ECOSYSTEM","events":[{"introduced":"2.32.0"},{"fixed":"2.56"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details