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

cilium

cilium

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 CVE identity is linked to the Lifecycle record Cilium. Use that record for publisher support phases and retirement dates.

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-56743 15 Jul 2026 >= 1.19.0, < 1.19.5 1.19.5. Update reference ↗
CVE-2026-56742 15 Jul 2026 < 1.17.17; >= 1.18.0, < 1.18.11; >= 1.19.0, < 1.19.5 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-49445 15 Jul 2026 < 1.17.14; >= 1.18.0, < 1.18.8; >= 1.19.0, < 1.19.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-2026-53935 7 Jul 2026 < 1.17.16; >= 1.18.2, < 1.18.10; >= 1.19.0, < 1.19.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-41520 8 May 2026 < 1.17.15; >= 1.18.0, < 1.18.9; >= 1.19.0, < 1.19.3 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-33726 27 Mar 2026 < 1.17.14; >= 1.18.0, < 1.18.8; >= 1.19.0, < 1.19.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-2026-26963 19 Feb 2026 >= 1.18.0, < 1.18.6 1.18.6. Update reference ↗
CVE-2025-64715 29 Nov 2025 < 1.16.17; >= 1.17.0, < 1.17.10; >= 1.18.0, < 1.18.4 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-2025-32793 21 Apr 2025 >= v1.13.0, < v1.15.16; >= v1.16.0, < v1.16.9; >= v1.17.0, < v1.17.3 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-2025-30163 24 Mar 2025 >= 1.16.0, < 1.16.8; >= 1.17.0, < 1.17.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-2025-30162 24 Mar 2025 >= 1.16.0, < 1.16.8; >= 1.17.0, < 1.17.2; >= 1.15.0, < 1.15.15 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-2025-23047 22 Jan 2025 >= 1.14.0, < 1.14.18; >= 1.15.0, < 1.15.12; >= 1.16.0, < 1.16.5 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-2025-23028 22 Jan 2025 >= 1.14.0, < 1.14.18; >= 1.15.0, < 1.15.12; >= 1.16.0, < 1.16.5 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-2024-52529 25 Nov 2024 >= 1.16.0, < 1.16.4 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-2024-47825 21 Oct 2024 >= 1.15.0, < 1.15.10; >= 1.14.0, < 1.14.16 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-42486 16 Aug 2024 = 1.16.0; >= 1.15.0, < 1.15.8 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-2024-42488 15 Aug 2024 < 1.14.14; >= 1.15.0, < 1.15.8 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-2024-42487 15 Aug 2024 = 1.16.0; >= 1.15.0, < 1.15.8 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-2024-37307 13 Jun 2024 >= 1.13.0, < 1.13.17; >= 1.14.0, < 1.14.12; >= 1.15.0, < 1.15.6 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-2024-28860 27 Mar 2024 >= 1.4.0, <= 1.13.14; >= 1.14.0, < 1.14.9; >= 1.15.0, < 1.15.3 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-2024-28250 18 Mar 2024 >= 1.14.0, < 1.14.8; >= 1.15.0, < 1.15.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-28249 18 Mar 2024 < 1.13.13; >= 1.14.0, < 1.14.8; >= 1.15.0, < 1.15.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-28248 18 Mar 2024 >= 1.13.9, < 1.13.13; >= 1.14.0, < 1.14.8; >= 1.15.0, < 1.15.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-25631 20 Feb 2024 < 1.14.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-25630 20 Feb 2024 >= 1.14.0, < 1.14.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41332 26 Sep 2023 >= 1.14.0, < 1.14.2; >= 1.13.0, < 1.13.7; < 1.12.14 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-41333 26 Sep 2023 >= 1.14.0, < 1.14.2; >= 1.13.0, < 1.13.7; < 1.12.14 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-39347 26 Sep 2023 >= 1.14.0, < 1.14.2; >= 1.13.0, < 1.13.7 ; < 1.12.14 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34242 15 Jun 2023 < 1.13.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-30851 25 May 2023 < 1.11.16; >= 1.12.0, < 1.12.9; >= 1.13.0, < 1.13.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-29002 18 Apr 2023 >= 1.7, < 1.11.16; >= 1.12.0, < 1.12.9; >= 1.13.0, < 1.13.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-27595 17 Mar 2023 = 1.13.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-27594 17 Mar 2023 < 1.11.15; >= 1.12.0, < 1.12.8; >= 1.13.0, < 1.13.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-27593 17 Mar 2023 < 1.11.15; >= 1.12.0, < 1.12.8; >= 1.13.0, < 1.13.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29179 20 May 2022 < 1.9.16; >= 1.10.0, < 1.10.11; >= 1.11.0, < 1.11.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29178 20 May 2022 < 1.9.16; >= 1.10.0, < 1.10.11; >= 1.11.0, < 1.11.5 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗

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.