Interpreter crash via dangling lexer token pointer
Published Feb 18, 2026 · Updated Feb 18, 2026
Use-after-free in Lily 2.0 through 2.3 allows local users to crash the interpreter by running a crafted Lily source file. During expression parsing, resolve_module advances the lexer and grow_source_buffer reallocates its buffer while expr_word retains a token pointer; shorthash_for_name then reads through that dangling pointer. The public reproducer triggers an AddressSanitizer abort on Linux x86_64, so the demonstrated consequence is an interpreter crash rather than code execution.
Summary
What happened
Use-after-free in Lily 2.0 through 2.3 allows local users to crash the interpreter by running a crafted Lily source file. During expression parsing, resolve_module advances the lexer and grow_source_buffer reallocates its buffer while expr_word retains a token pointer; shorthash_for_name then reads through that dangling pointer. The public reproducer triggers an AddressSanitizer abort on Linux x86_64, so the demonstrated consequence is an interpreter crash rather than code execution.
The record
- CVE
- CVE-2026-2660
- Published
- Feb 18, 2026
- Updated
- Feb 18, 2026
- Vendor
- FascinatedBox
- Product
- Lily
- Classifications
- CWE-119, CWE-416, T1499
- 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=2.0
- Affected versionversion=2.1
- Affected versionversion=2.2
- Affected versionversion=2.3
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
- repro.lily heap-use-after-free reproducerproof 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