Code execution via crafted .ctl file
Published Jun 18, 2026 · Updated Jun 18, 2026
Type confusion in AzeoTech DAQFactory 21.1 and earlier allows context-dependent attackers to execute code through a crafted .ctl file. The public advisory identifies .ctl file handling as the trigger but does not disclose the parser object, confused types, or invalid operation. Exploitation is local and requires a user to open the file; resulting code runs in the DAQFactory process context.
Summary
What happened
Type confusion in AzeoTech DAQFactory 21.1 and earlier allows context-dependent attackers to execute code through a crafted .ctl file. The public advisory identifies .ctl file handling as the trigger but does not disclose the parser object, confused types, or invalid operation. Exploitation is local and requires a user to open the file; resulting code runs in the DAQFactory process context.
The record
- CVE
- CVE-2026-12390
- Published
- Jun 18, 2026
- Updated
- Jun 18, 2026
- Vendor
- AzeoTech
- Product
- DAQFactory
- Classifications
- CWE-843, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 18, 2026CVE publishedPublication date reported by the CVE source.
- Jun 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=21.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo