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

Centreon

Infra Monitoring

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-14453 13 Jul 2026 24.10.0 < 24.10.14; 25.10.0 < 25.10.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-15029 5 Jan 2026 Infra Monitoring: 25.10.0 < 25.10.2, 24.10.0 < 24.10.3, 24.04.0 < 24.04.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-15026 5 Jan 2026 Infra Monitoring: 25.10.0 < 25.10.2, 24.10.0 < 24.10.3, 24.04.0 < 24.04.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-12511 5 Jan 2026 25.10.0 < 25.10.1; 24.10.0 < 24.10.4; 24.04.0 < 24.04.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-2025-12513 5 Jan 2026 25.10.0 < 25.10.2; 24.10.0 < 24.10.15; 24.04.0 < 24.04.19 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-12519 5 Jan 2026 25.10.0 < 25.10.2; 24.10.0 < 24.10.15; 24.04.0 < 24.04.19 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-13056 5 Jan 2026 25.10.0 < 25.10.2; 24.10.0 < 24.10.15; 24.04.0 < 24.04.19 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-5965 5 Jan 2026 Infra Monitoring: 25.10.0 < 25.10.2, 24.10.0 < 24.10.15, 24.04.0 < 24.04.19 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-54890 22 Dec 2025 24.10.0 < 24.10.15; 24.04.0 < 24.04.19; 23.10.0 < 23.10.29 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-8460 22 Dec 2025 24.10.0 < 24.10.5; 24.04.0 < 24.04.5; 23.10.0 < 23.10.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-10023 27 Oct 2025 Infra Monitoring: 24.10.0 < 24.10.9, 24.04.0 < 24.04.16, 23.10.0 < 23.10.26 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-8432 27 Oct 2025 Infra Monitoring: 24.10.0 < 24.10.6, 24.04.0 < 24.04.9, 23.10.0 < 23.10.15 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-8459 14 Oct 2025 Infra Monitoring: 24.10.0 < 24.10.13, 24.04.0 < 24.04.18, 23.10.0 < 23.10.28 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-8430 14 Oct 2025 Infra Monitoring: 24.10.0 < 24.10.13, 24.04.0 < 24.04.18, 23.10.0 < 23.10.28 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-8429 14 Oct 2025 Infra Monitoring: 24.10.0 < 24.10.13, 24.04.0 < 24.04.18, 23.10.0 < 23.10.28 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54893 14 Oct 2025 Infra Monitoring: 24.10.0 < 24.10.13, 24.04.0 < 24.04.18, 23.10.0 < 23.10.28 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54891 14 Oct 2025 Infra Monitoring: 24.10.0 < 24.10.13, 24.04.0 < 24.04.18, 23.10.0 < 23.10.28 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54892 14 Oct 2025 Infra Monitoring: 24.10.0 < 24.10.13, 24.04.0 < 24.04.18, 23.10.0 < 23.10.28 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54889 14 Oct 2025 Infra Monitoring: 24.10.0 < 24.10.13, 24.04.0 < 24.04.18, 23.10.0 < 23.10.28 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-5946 14 Oct 2025 Infra Monitoring: 24.10.0 < 24.10.13, 24.04.0 < 24.04.18, 23.10.0 < 23.10.28 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-8428 14 Oct 2025 Infra Monitoring: 24.10.0 < 24.10.13, 24.04.0 < 24.04.18, 23.10.0 < 23.10.28 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.