AzeoTech
DAQFactory
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-12921 | 25 Jun 2026 | ≤ 21.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-12390 | 18 Jun 2026 | ≤ 21.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-66585 | 11 Dec 2025 | ≤ Release 20.7 (Build 2555) | Release 21.1 | Update reference ↗ |
| CVE-2025-66586 | 11 Dec 2025 | ≤ Release 20.7 (Build 2555) | Release 21.1 | Update reference ↗ |
| CVE-2025-66588 | 11 Dec 2025 | ≤ Release 20.7 (Build 2555) | Release 21.1 | Update reference ↗ |
| CVE-2025-66589 | 11 Dec 2025 | DAQFactory: ≤ Release 20.7 (Build 2555) | AzeoTech has released the following update that addresses these issues:; * DAQFactory: Release 21.1; AzeoTech also recommends users take the following actions to reduce the risk:; * Users are discouraged from using documents from unknown/untrusted sources.; * Users are encouraged to store .ctl files in a folder only writeable by admin-level users.; * Users are encouraged to operate in “Safe Mode” when loading documents that have been out of their control.; * Users are encouraged to apply a document editing password to their documents. | Update reference ↗ |
| CVE-2025-66590 | 11 Dec 2025 | ≤ Release 20.7 (Build 2555) | Release 21.1 | Update reference ↗ |
| CVE-2021-42698 | 5 Nov 2021 | All versions ≤ New version | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-42701 | 5 Nov 2021 | All versions ≤ New version | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-42543 | 5 Nov 2021 | All versions ≤ New version | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-42699 | 5 Nov 2021 | All versions ≤ New version | 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.