Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious .ctl project file
-
DeliveryDeliver via email or shared storage
-
ExploitOperator opens file in DAQFactory
-
ExecutionTrigger use-after-free in parser
-
PersistHijack dangling pointer
-
ImpactExecute arbitrary code on HMI host
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a victim to open a specially crafted .ctl (DAQFactory control/project) file in AzeoTech DAQFactory version 21.1 or earlier - the malicious file format is the exact trigger named in the advisory. The CVSS vector confirms active user interaction is mandatory (UI:A) and the vector is local (AV:L), so there is no remote, network-facing exploitation path; the attacker must get the crafted file onto the host and have an operator open it. Limiting factors that reduce real-world risk: dependence on operator action/social engineering, local file delivery, and confinement to vulnerable DAQFactory versions. No special product configuration or feature toggle is called out beyond using DAQFactory to open the file. |
| Impact | Signals are largely consistent and point to a real but operator-gated risk rather than a mass-exploitable internet threat. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H) shows a local attack vector with required active user interaction and no privileges, yielding high impact across all three pillars and a base score of 8.4. Because exploitation depends on a victim opening a malicious .ctl file, it cannot be automated network-wide and relies on social engineering or delivery of a tampered project file, which lowers practical likelihood relative to the raw score. No EPSS value was supplied, there is no public exploit identified at time of analysis, and the CVE is not in CISA KEV, so there is no evidence of active exploitation; the realistic model is a targeted ICS engineer being induced to open a crafted project file. Verification gap: no fixed version is present in the supplied data, so remediation status must be confirmed against the CISA ICS advisory. |
| Exploit ScenarioDerived | An attacker delivers a DAQFactory project file (.ctl) crafted to trigger the use-after-free, posing as an updated HMI screen or control configuration. When an engineer opens the file in DAQFactory on the workstation, the dangling pointer is exploited to execute attacker code in the application's context, establishing a foothold on the control-system host. Local attack vector plus required user interaction (AV:L/UI:A) means the attack hinges on social engineering rather than remote automation, and no public PoC has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 25, 2026
Arbitrary code execution in AzeoTech DAQFactory (versions 21.1 and prior) arises from a use-after-free flaw triggered when the application parses a maliciously crafted .ctl project/control file. An attacker who can convince an operator to open a booby-trapped .ctl file can corrupt memory and run code in the context of the DAQFactory process on the engineering or HMI workstation. No public exploit is identified at time of analysis and the CVE is not in CISA KEV, but it carries a high CVSS 4.0 base score of 8.4 driven by full confidentiality, integrity, and availability impact.
RemediationAI
No vendor-released patch version is identified in the available data, so the fixed release must be confirmed directly from AzeoTech and the CISA ICS advisory at https://www.cisa.gov/news-events/ics-advisories/icsa-26-169-02 (ICSA-26-169-02); upgrade to the vendor-designated fixed version once confirmed. As compensating controls until patching, treat .ctl files as untrusted executable content: only open project/control files from known-good, integrity-verified sources and block delivery of .ctl files via email and web gateways (trade-off: friction when legitimately exchanging project files). Restrict who can place files on engineering/HMI workstations and apply application allowlisting and least-privilege so a DAQFactory compromise does not yield broader host control. Isolate DAQFactory hosts on a segmented OT network without general internet or email access to reduce the chance an operator ever receives and opens a malicious file.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
DAQFactory is a Windows-based HMI/SCADA and data-acquisition runtime used to build operator interfaces, alarms, logging, and device communication in industrial control environments. The vulnerability is a CWE-416 Use After Free: the application continues to reference a heap object after it has been freed while loading/deserializing a .ctl file (DAQFactory's control/project document format). When attacker-controlled data influences the freed-then-reused allocation, the dangling pointer can be steered to attacker-supplied data, converting memory corruption into control-flow hijack and code execution. The CPE cpe:2.3:a:azeotech:daqfactory confirms the affected component is the DAQFactory application itself rather than a bundled third-party library.
Know when Daqfactory gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Local file-open vector (AV:L) with mandatory operator action (UI:R) and no prior privileges (PR:N); code execution yields full C/I/A impact in an unchanged scope.
Primary rating from Vendor (icscert).
CVSS VectorVendor: icscert
DescriptionCVE.org
In AzeoTech DAQFactory versions 21.1 and prior, a Use After Free vulnerability can be exploited by an attacker using specially crafted .ctl files which can result in code execution.
Zero Day Initiative Advisories
Executive ViewAI
AzeoTech DAQFactory versions 21.1 and earlier are vulnerable to arbitrary code execution when operators open crafted project files, creating direct risk to engineering and process control workstations. Without a vendor patch, HMI and SCADA operators remain exposed to attacks that could compromise process visibility and operational continuity.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict .ctl file origin via firewall and endpoint policy-block external file transfers; (2) Isolate critical HMI workstations on segmented networks; (3) Implement application whitelisting to prevent unauthorized process spawning; (4) Enable file integrity monitoring on project file repositories; (5) Require operator escalation for .ctl file opening from non-standard sources.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Daqfactory
View allCode execution in AzeoTech DAQFactory versions 21.1 and prior is achievable when a user opens a maliciously crafted .ctl
Out-of-bounds read in AzeoTech DAQFactory 20.7 (Build 2555) allows local attackers to disclose sensitive process memory
Out-of-bounds write in AzeoTech DAQFactory release 20.7 (Build 2555) enables arbitrary code execution or denial of servi
Arbitrary code execution in AzeoTech DAQFactory release 20.7 (Build 2555) is possible when a local user opens or interac
Project files are stored memory objects in the form of binary serialized data that can later be read and deserialized ag
The affected application uses specific functions that could be abused through a crafted project file, which could lead t
Local code execution in AzeoTech DAQFactory release 20.7 (Build 2555) is possible when a user opens a maliciously crafte
Type confusion in AzeoTech DAQFactory 20.7 (Build 2555) enables arbitrary code execution when a user opens a maliciously
An Incorrect Default Permissions issue was discovered in AzeoTech DAQFactory versions prior to 17.1. Rated high severity
An attacker could prepare a specially crafted project file that, if opened, would attempt to connect to the cloud and tr
The affected product is vulnerable to cookie information being transmitted as cleartext over HTTP. Rated medium severity
An Uncontrolled Search Path Element issue was discovered in AzeoTech DAQFactory versions prior to 17.1. Rated medium sev
EUVD-2026-39513
GHSA-3mp5-47hq-xq78
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB