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

ABB

ABB AbilityTM zenon

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-2025-8754 13 Aug 2025 7.50 ≤ 14 The issue has been corrected in the following ABB Ability™ zenon product versions: Version 11 build 400376, Version 12 build 407620 and Version 14 build 405141, where the respective patches have been successfully released. ABB recommends that customers upgrade to these patched versions at the earliest convenience. The updated versions are available through the zenon Update Manager (Versions 12 and 14). For Version 11, please contact zenon.support@abb.com. Update reference ↗
CVE-2023-3324 24 Jul 2023 11 build ≤ 11 build 106404 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-3323 24 Jul 2023 11 build ≤ 11 build 106404 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-3322 24 Jul 2023 11 build ≤ 11 build 106404 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-3321 24 Jul 2023 11 build ≤ 11 build 106404 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.