Code execution via use-after-free in CTL parser
Published Dec 11, 2025 · Updated Dec 11, 2025
Use-after-free in AzeoTech DAQFactory 20.7 (Build 2555) and earlier allows attackers to execute code through a crafted .ctl file. The .ctl file parser accesses memory after its underlying object has been freed, corrupting process memory; no narrower function or object has been disclosed. Exploitation requires a user to load an attacker-supplied document, and successful memory corruption executes code with the current process's privileges.
Summary
What happened
Use-after-free in AzeoTech DAQFactory 20.7 (Build 2555) and earlier allows attackers to execute code through a crafted .ctl file. The .ctl file parser accesses memory after its underlying object has been freed, corrupting process memory; no narrower function or object has been disclosed. Exploitation requires a user to load an attacker-supplied document, and successful memory corruption executes code with the current process's privileges.
The record
- CVE
- CVE-2025-66585
- Published
- Dec 11, 2025
- Updated
- Dec 11, 2025
- Vendor
- AzeoTech
- Product
- DAQFactory
- Classifications
- CWE-416, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 2025CVE publishedPublication date reported by the CVE source.
- Dec 11, 2025Record 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 <=Release 20.7 (Build 2555)
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