Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY37 SECURITY RECORDS

Kimai

Kimai

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-52827 15 Sep 2026 kimai: < 2.59.0 2.59.0. Update reference ↗
CVE-2026-52822 15 Sep 2026 kimai: < 2.58.0 2.58.0. Update reference ↗
CVE-2026-52828 15 Sep 2026 kimai: < 2.58.0 2.58.0. Update reference ↗
CVE-2026-52826 15 Sep 2026 kimai: < 2.57.0 2.57.0. Update reference ↗
CVE-2026-52823 15 Sep 2026 kimai: < 2.58.0 2.58.0. Update reference ↗
CVE-2026-52824 15 Sep 2026 kimai: < 2.58.0 2.58.0. Update reference ↗
CVE-2026-52825 15 Sep 2026 kimai: < 2.58.0 2.58.0. Update reference ↗
CVE-2026-52821 15 Sep 2026 kimai: < 2.57.0 2.57.0. Update reference ↗
CVE-2026-52820 15 Sep 2026 kimai: < 2.57.0 2.57.0. Update reference ↗
CVE-2026-52819 15 Sep 2026 kimai: < 2.57.0 2.57.0. Update reference ↗
CVE-2026-49992 11 Sep 2026 kimai: < 2.58.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-49865 11 Sep 2026 kimai: < 2.58.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84808 2 Sep 2026 < 2.65.0 2.65.0 Update reference ↗
CVE-2026-84807 2 Sep 2026 < 2.65.0 2.65.0 Update reference ↗
CVE-2026-84806 2 Sep 2026 < 2.63.0 2.63.0 Update reference ↗
CVE-2026-84805 2 Sep 2026 2.61.0 < 2.63.0 2.63.0 Update reference ↗
CVE-2026-84804 2 Sep 2026 < 2.65.0 2.65.0 Update reference ↗
CVE-2026-80202 25 Aug 2026 < 2.56.0 2.56.0 Update reference ↗
CVE-2026-80201 25 Aug 2026 < 2.53.0 2.53.0 Update reference ↗
CVE-2026-80200 25 Aug 2026 < 2.53.0 2.53.0 Update reference ↗
CVE-2026-80199 25 Aug 2026 < 2.54.0 2.54.0 Update reference ↗
CVE-2026-80198 25 Aug 2026 < 2.56.0 2.56.0 Update reference ↗
CVE-2026-80197 25 Aug 2026 < 2.57.0 2.57.0 Update reference ↗
CVE-2026-80196 25 Aug 2026 < 2.58.0 2.58.0 Update reference ↗
CVE-2026-80195 25 Aug 2026 < 2.63.0 2.63.0 Update reference ↗
CVE-2026-80194 25 Aug 2026 < 2.64.0 2.64.0 Update reference ↗
CVE-2026-80193 25 Aug 2026 < 2.62.0 2.62.0 Update reference ↗
CVE-2026-44298 8 May 2026 >= 2.32.0, < 2.56.0 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-41498 8 May 2026 < 2.54.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-42267 8 May 2026 >= 2.27.0, < 2.54.0 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-40486 17 Apr 2026 < 2.53.0 2.53.0. Update reference ↗
CVE-2026-40479 17 Apr 2026 >= 1.16.3, < 2.53.0 2.53.0. Update reference ↗
CVE-2026-28685 6 Mar 2026 < 2.51.0 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-23626 18 Jan 2026 < 2.46.0 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2023-53957 19 Dec 2025 1.30.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-29200 28 Mar 2024 < 2.13.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-46245 31 Oct 2023 < 2.1.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.