Code execution via CO file type confusion
Published Sep 17, 2025 · Updated Sep 17, 2025
Type confusion in the CO file parser in Ashlar-Vellum Cobalt 12 SP1 allows attackers to execute code via a crafted CO file. The parser fails to validate user-supplied CO data before using it as the expected type, causing an incompatible interpretation of the file. Exploitation requires a user to visit a malicious page or open the file, after which code runs in the context of the Cobalt process.
Summary
What happened
Type confusion in the CO file parser in Ashlar-Vellum Cobalt 12 SP1 allows attackers to execute code via a crafted CO file. The parser fails to validate user-supplied CO data before using it as the expected type, causing an incompatible interpretation of the file. Exploitation requires a user to visit a malicious page or open the file, after which code runs in the context of the Cobalt process.
The record
- CVE
- CVE-2025-8002
- Published
- Sep 17, 2025
- Updated
- Sep 17, 2025
- Vendor
- Ashlar-Vellum
- Product
- Cobalt
- Classifications
- CWE-843, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2025CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=12 SP1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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