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

Delta Electronics

DIAEnergie

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-2022-26338 29 Mar 2022 unspecified < 1.8.02.004 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-26514 29 Mar 2022 unspecified < 1.8.02.004 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-26666 29 Mar 2022 unspecified < 1.8.02.004 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-26887 29 Mar 2022 unspecified < 1.8.02.004 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-26836 29 Mar 2022 unspecified < 1.8.02.004 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-26349 29 Mar 2022 unspecified < 1.8.02.004 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-26065 29 Mar 2022 unspecified < 1.8.02.004 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-26013 29 Mar 2022 unspecified < 1.8.02.004 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-25880 29 Mar 2022 unspecified < 1.8.02.004 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-0923 29 Mar 2022 unspecified < 1.8.02.004 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-26069 29 Mar 2022 unspecified < 1.8.02.004 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-25347 29 Mar 2022 unspecified < 1.8.02.004 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-25980 29 Mar 2022 unspecified < 1.8.02.004 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-26059 29 Mar 2022 unspecified < 1.8.02.004 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-0988 25 Mar 2022 unspecified ≤ 1.7.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-2021-23228 22 Dec 2021 All ≤ 1.7.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31558 22 Dec 2021 All ≤ 1.7.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-44544 22 Dec 2021 All ≤ 1.7.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-44471 22 Dec 2021 All ≤ 1.7.5 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.