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

Apache Software Foundation

Apache Kylin

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-62393 14 Jul 2026 4 ≤ 5.0.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-62392 14 Jul 2026 4 ≤ 5.0.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-62390 14 Jul 2026 4 ≤ 5.0.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-61735 2 Oct 2025 4.0.0 ≤ 5.0.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-61733 2 Oct 2025 4.0.0 ≤ 5.0.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-61734 2 Oct 2025 4.0.0 ≤ 5.0.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-30067 27 Mar 2025 4.0.0 ≤ 5.0.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-48944 27 Mar 2025 5.0.0 ≤ 5.0.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23590 4 Nov 2024 2.0.0 < 5.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-29055 29 Jan 2024 2.0.0 ≤ 4.0.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-44621 30 Dec 2022 Apache Kylin 4 ≤ 4.0.2 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-2022-43396 30 Dec 2022 Apache Kylin 4 ≤ 4.0.2 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-2022-24697 13 Oct 2022 Apache Kylin 2 < 2.6.6; Apache Kylin 3 ≤ 3.1.2; Apache Kylin 4 ≤ 4.0.1 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-2021-45458 6 Jan 2022 Apache Kylin 2 ≤ 2.6.6; Apache Kylin 3 ≤ 3.1.2; Apache Kylin 4 ≤ 4.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-45457 6 Jan 2022 Apache Kylin 2 ≤ 2.6.6; Apache Kylin 3 ≤ 3.1.2; Apache Kylin 4 ≤ 4.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-45456 6 Jan 2022 Apache Kylin 4 4.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-36774 6 Jan 2022 Apache Kylin 2 ≤ 2.6.6; Apache Kylin 3 ≤ 3.1.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31522 6 Jan 2022 Apache Kylin 2 ≤ 2.6.6; Apache Kylin 3 ≤ 3.1.2; Apache Kylin 4 ≤ 4.0.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-2021-27738 6 Jan 2022 Apache Kylin 3 < 3.1.2 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.