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

Accusoft

ImageGear

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-23567 25 Sep 2023 20.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-28393 25 Sep 2023 20.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-32614 25 Sep 2023 20.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-32284 25 Sep 2023 20.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-35002 25 Sep 2023 20.1 Update to V2.95.3.23 or later version Update reference ↗
CVE-2023-32653 25 Sep 2023 20.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-39453 25 Sep 2023 20.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-40163 25 Sep 2023 20.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-32588 9 Nov 2022 20.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29465 5 Aug 2022 20.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-23400 3 May 2022 19.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-22137 3 May 2022 19.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-40398 14 Apr 2022 19.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-21949 14 Apr 2022 19.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-21947 14 Apr 2022 19.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-21946 14 Apr 2022 19.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-21945 14 Apr 2022 19.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-21944 14 Apr 2022 19.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-21943 14 Apr 2022 19.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-21942 14 Apr 2022 19.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-21939 14 Apr 2022 19.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-21938 14 Apr 2022 19.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-21914 14 Apr 2022 19.10 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.