Code execution via unchecked CO file length
Published Oct 29, 2025 · Updated Oct 29, 2025
Heap-based buffer overflow in Ashlar-Vellum Cobalt 1204.97 allows remote attackers to execute code through a crafted CO file. The CO file parser copies user-supplied data into a heap buffer without first validating that its length fits the destination. Exploitation requires the target to open a malicious file or visit a malicious page, and successful code runs in the current process.
Summary
What happened
Heap-based buffer overflow in Ashlar-Vellum Cobalt 1204.97 allows remote attackers to execute code through a crafted CO file. The CO file parser copies user-supplied data into a heap buffer without first validating that its length fits the destination. Exploitation requires the target to open a malicious file or visit a malicious page, and successful code runs in the current process.
The record
- CVE
- CVE-2025-11464
- Published
- Oct 29, 2025
- Updated
- Oct 29, 2025
- Vendor
- Ashlar-Vellum
- Product
- Cobalt
- Classifications
- CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2025CVE publishedPublication date reported by the CVE source.
- Oct 29, 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=1204.97
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.
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