# CVE-2026-23626: Kimai Vulnerable to Authenticated Server-Side Template Injection (SSTI)

> Authenticated users can exploit Server-Side Template Injection in Kimai's export feature to extract sensitive data like password hashes and session tokens.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/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:** 18 Jan 2026
- **Updated:** 20 Jan 2026
- **Also known as:** GHSA-jg2j-2w24-54cg

## What is CVE-2026-23626?

CVE-2026-23626 is a medium-severity code injection vulnerability in kimai, published on 18 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Kimai is a web-based multi-user time-tracking application. Prior to version 2.46.0, Kimai's export functionality uses a Twig sandbox with an overly permissive security policy (`DefaultPolicy`) that allows arbitrary method calls on objects available in the template context. An authenticated user with export permissions can deploy a malicious Twig template that extracts sensitive information including environment variables, all user password hashes, serialized session tokens, and CSRF tokens. Version 2.46.0 patches this issue.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

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

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.46.0 |
| `kimai/kimai` | Packagist | All versions | 2.46.0 |

Products: Kimai Kimai.

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

Upgrade kimai/kimai to 2.46.0 or later.

## Is CVE-2026-23626 being exploited?

There is no known exploitation of CVE-2026-23626 in the wild and no public exploit code.

## 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-2024-29200](https://insights.sbomify.com/CVE-2024-29200/): API returns timesheet entries a user should not be authorized to view (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23626 and fix it if it is affected.

What it is: CVE-2026-23626 is a medium-severity code injection vulnerability in kimai, published on 18 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23626 in the wild and no public exploit code.

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

## Sources

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

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