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

Centreon

Centreon

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 Centreon. 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-2025-3872 24 Apr 2025 22.10.0 < 22.10.28; 23.04.0 < 23.04.25; 23.10.0 < 23.10.20; 24.04.0 < 24.04.10; 24.10.0 < 24.10.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-5725 21 Aug 2024 23.10.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-5723 21 Aug 2024 23.10.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51633 3 May 2024 23.04 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-23119 1 Apr 2024 23.10.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-2024-23118 1 Apr 2024 23.10.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-2024-23117 1 Apr 2024 23.10.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-2024-23116 1 Apr 2024 23.10.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-2024-23115 1 Apr 2024 23.10.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-2024-0637 1 Apr 2024 23.10.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-2022-42429 29 Mar 2023 22.04 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-42428 29 Mar 2023 22.04 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-42427 29 Mar 2023 22.04 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-42426 29 Mar 2023 22.04 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-42425 29 Mar 2023 22.04 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-42424 29 Mar 2023 22.04 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-41142 26 Jan 2023 22.04.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-34872 3 Aug 2022 21.10-2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-34871 3 Aug 2022 21.10-2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2012-5967 19 Dec 2012 Centreon: 2.3.3 through 2.3.9-4; Centreon web: fixed in 2.6.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.