# CVE-2026-44298: Kimai has an arbitrary file read in its invoice PDF renderer (admin)

Source: https://junglewise.ai/threats/cve-2026-44298-kimai-has-an-arbitrary-file-read-in-its-invoice-pdf-renderer  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-08  
License: CC BY 4.0 with a link back

CVE-2026-44298 · Severity: medium · CVSS 4.1 · Published 2026-05-08

Kimai is an open-source time tracking application. From version 2.32.0 to before version 2.56.0, 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. This issue has been patched in version 2.56.0.

Technologies: [Kimai](https://junglewise.ai/threats/technologies/kimai), [kimai/kimai (Packagist)](https://junglewise.ai/threats/technologies/kimai-kimai). Vendors: [Kimai](https://junglewise.ai/threats/vendors/kimai), [Packagist](https://junglewise.ai/threats/vendors/packagist).

## Quick answers

**Is CVE-2026-44298 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-44298 being exploited in the wild.

**How severe is CVE-2026-44298?** Medium severity, with a CVSS score of 4.1, published 8 May 2026.

**Which products and versions are affected?** kimai/kimai (Packagist) ECOSYSTEM:introduced=2.32.0,fixed=2.56.

**Is there a fix for CVE-2026-44298?** Yes. kimai/kimai (Packagist): upgrade to 2.56 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-44298?** Check whether you run Kimai or kimai/kimai (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- kimai/kimai (Packagist): upgrade to 2.56 or later

  ```sh
  composer require kimai/kimai:^2.56
  ```


## Affected products

- Kimai
- kimai/kimai (Packagist) ECOSYSTEM:introduced=2.32.0,fixed=2.56

## Identifiers

- CVE-2026-44298
- GHSA-h5fh-7hwr-97mw

## Related threats

- [Kimai missing authorization check in ExportController export templates](https://junglewise.ai/threats/cve-2026-52828-kimai-missing-authorization-check-in-exportcontroller-export)
- [Kimai 2FA bypass in REST API via session cookie replay](https://junglewise.ai/threats/cve-2026-52827-kimai-2fa-bypass-in-rest-api-via-session-cookie-replay)
- [Kimai improper authorization in rate edit endpoints](https://junglewise.ai/threats/cve-2026-52826-kimai-improper-authorization-in-rate-edit-endpoints)
- [Kimai improper authorization in Team assignment APIs](https://junglewise.ai/threats/cve-2026-52825-kimai-improper-authorization-in-team-assignment-apis)
- [Kimai insecure default APP_SECRET in Docker image](https://junglewise.ai/threats/cve-2026-52824-kimai-insecure-default-app-secret-in-docker-image)