Code execution via malformed CO file parsing
Published Aug 18, 2025 · Updated Aug 19, 2025
Out-of-bounds write in CO-file parsing in Ashlar-Vellum CAD applications before 12.6.1204.204 allows attackers to execute code. The CO parser uses attacker-controlled file data without adequate validation, causing a write beyond an allocated buffer. Exploitation requires a local user to open a crafted CO file in Cobalt, Xenon, Argon, Lithium CAD, or Cobalt Share, after which code runs with the current process's privileges.
Summary
What happened
Out-of-bounds write in CO-file parsing in Ashlar-Vellum CAD applications before 12.6.1204.204 allows attackers to execute code. The CO parser uses attacker-controlled file data without adequate validation, causing a write beyond an allocated buffer. Exploitation requires a local user to open a crafted CO file in Cobalt, Xenon, Argon, Lithium CAD, or Cobalt Share, after which code runs with the current process's privileges.
The record
- CVE
- CVE-2025-53705
- Published
- Aug 18, 2025
- Updated
- Aug 19, 2025
- Vendor
- Ashlar-Vellum
- Product
- Cobalt
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2025CVE publishedPublication date reported by the CVE source.
- Aug 19, 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 <12.6.1204.204
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