Code execution via unchecked VS file length
Published Sep 15, 2026 · Updated Sep 15, 2026
Heap-based buffer overflow in Ashlar-Vellum Cobalt 1204.204 allows remote attackers to execute code through a crafted VS file. The VS parser copies user-supplied data into a heap buffer without first validating its length, allowing the copy to exceed the allocation. Exploitation requires the target to open the file or visit a page that supplies it, and code runs in the context of the current process.
Summary
What happened
Heap-based buffer overflow in Ashlar-Vellum Cobalt 1204.204 allows remote attackers to execute code through a crafted VS file. The VS parser copies user-supplied data into a heap buffer without first validating its length, allowing the copy to exceed the allocation. Exploitation requires the target to open the file or visit a page that supplies it, and code runs in the context of the current process.
The record
- CVE
- CVE-2026-19781
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- Ashlar-Vellum
- Product
- Cobalt
- Classifications
- T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 2026Record 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.204
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