Application crash via asynchronous teardown race
Published Feb 18, 2026 · Updated Feb 18, 2026
Use-after-free in ChaiScript 6.0 and 6.1.0 allows local users to crash a host application through concurrent script execution. During engine teardown, detached async workers continue undefined-variable lookups in a shared symbol map after the main thread frees its nodes, so str_less reads a released string key. Exploitation requires local low-privileged access and a timing-dependent race; the demonstrated consequence is an availability-only crash.
Summary
What happened
Use-after-free in ChaiScript 6.0 and 6.1.0 allows local users to crash a host application through concurrent script execution. During engine teardown, detached async workers continue undefined-variable lookups in a shared symbol map after the main thread frees its nodes, so str_less reads a released string key. Exploitation requires local low-privileged access and a timing-dependent race; the demonstrated consequence is an availability-only crash.
The record
- CVE
- CVE-2026-2655
- Published
- Feb 18, 2026
- Updated
- Feb 18, 2026
- Vendor
- ChaiScript
- Product
- ChaiScript
- Classifications
- CWE-416, CWE-119
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 18, 2026CVE publishedPublication date reported by the CVE source.
- Feb 18, 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=6.0
- Affected versionversion=6.1.0
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
- Upstream issue proof of conceptproof of concept · demonstrated
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