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

Artica PFMS

Pandora FMS

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-2023-0828 3 Oct 2023 v0 ≤ v767 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-24518 3 Oct 2023 v0 ≤ v767 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-24517 22 Aug 2023 v0 ≤ v767 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-24516 22 Aug 2023 v0 ≤ v767 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-24514 22 Aug 2023 v0 ≤ v767 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-24515 22 Aug 2023 v0 ≤ v767 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-2807 13 Jun 2023 v0 ≤ v771 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-47373 15 Feb 2023 v766 ≤ v766 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-47372 15 Feb 2023 ≤ v766 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-45437 15 Feb 2023 v765 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-45436 15 Feb 2023 v765 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-43980 27 Jan 2023 v765 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-43979 27 Jan 2023 v764 ≤ v764 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-43978 27 Jan 2023 v764 ≤ v764 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-46678 5 Aug 2022 v756 ≤ v756 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-46680 5 Aug 2022 v756 ≤ v756 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-46677 5 Aug 2022 v756 ≤ v756 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-46676 5 Aug 2022 v756 ≤ v756 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-46679 5 Aug 2022 v756 ≤ v756 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-46681 5 Aug 2022 v756 ≤ v756 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-26310 1 Aug 2022 v760 ≤ v760 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-26309 1 Aug 2022 v760 ≤ v760 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-26308 1 Aug 2022 v760 ≤ v760 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1648 26 Jul 2022 v760 ≤ v760 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2059 25 Jul 2022 v761 ≤ v761 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2032 25 Jul 2022 v761 ≤ v761 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-0507 9 Mar 2022 v759 < v759 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.