Interpreter crash via error-reporting buffer under-read
Published Mar 1, 2026 · Updated Mar 1, 2026
Out-of-bounds read in FascinatedBox Lily 2.0 through 2.3 allows local users to crash the interpreter with a crafted source file. In patch_line_end, error reporting reads one byte before an allocated source buffer while constructing a traceback for an error at an empty line or the buffer start. Exploitation requires local execution of crafted Lily source; the demonstrated consequence is an interpreter abort.
Summary
What happened
Out-of-bounds read in FascinatedBox Lily 2.0 through 2.3 allows local users to crash the interpreter with a crafted source file. In patch_line_end, error reporting reads one byte before an allocated source buffer while constructing a traceback for an error at an empty line or the buffer start. Exploitation requires local execution of crafted Lily source; the demonstrated consequence is an interpreter abort.
The record
- CVE
- CVE-2026-3390
- Published
- Mar 1, 2026
- Updated
- Mar 1, 2026
- Vendor
- FascinatedBox
- Product
- Lily
- Classifications
- CWE-125, CWE-119
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 1, 2026CVE publishedPublication date reported by the CVE source.
- Mar 1, 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 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