CVE-2026-12390
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn AzeoTech DAQFactory versions 21.1 and prior, a Type Confusion vulnerability can be exploited by an attacker using specially crafted .ctl files which can result in code execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAzeoTech DAQFactory versions 21.1 and prior contains a type confusion vulnerability that can be triggered by opening specially crafted .ctl files. The vulnerability allows an attacker to achieve arbitrary code execution on the affected system by exploiting the improper type handling during .ctl file parsing.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 21.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if AzeoTech DAQFactory is installedSearch for DAQFactory in installed programs on Windows (Control Panel > Programs and Features) or use registry queries under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for product entries containing 'DAQFactory' or 'AzeoTech'Affected if DAQFactory application is present on the system
-
Identify the installed DAQFactory versionLocate the DAQFactory executable (typically in Program Files or Program Files x86) and check its properties for the version, or look for version information in the Windows registry uninstall entryAffected if The installed version is 21.1 or any version prior to 21.1
-
Verify .ctl file handling capability existsCheck if the DAQFactory installation includes file parsing functionality capable of importing .ctl files, typically found in the application bin or support directoriesAffected if The application has the capability to parse .ctl files and this feature is accessible to users
-
Inspect for untrusted or unexpected .ctl filesSearch user-accessible directories (Documents, Downloads, shared network folders) for .ctl files, particularly those from unknown sources or recently modifiedAffected if There are .ctl files present that originated from untrusted or external sources
-
Review recent .ctl file import activityCheck DAQFactory application logs, Windows Event Viewer application logs, or file system audit logs for recent .ctl file import or parsing eventsAffected if There is evidence of recent .ctl file imports, especially from users with limited security awareness training
The environment is affected if AzeoTech DAQFactory version 21.1 or prior is installed and users have the ability to import or parse .ctl files from potentially untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a version newer than 21.1 when a patch becomes available from AzeoTech. Until then, avoid opening .ctl files from untrusted sources and implement network segmentation to limit exposure of systems running DAQFactory.
- Consultation6.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12390 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12390 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data