Local process crash via unbounded parser recursion
Published Mar 1, 2026 · Updated Mar 1, 2026
Uncontrolled recursion in the Wren 0.4.0 and earlier compiler allows local users to crash an embedding process with deeply nested source. The recursive-descent parser imposes no nesting limit, exhausting the C stack before resolveLocal calls bcmp with an invalid name pointer. Exploitation requires a low-privileged local user to supply source to an application embedding Wren; the demonstrated consequence is process termination under AddressSanitizer.
Summary
What happened
Uncontrolled recursion in the Wren 0.4.0 and earlier compiler allows local users to crash an embedding process with deeply nested source. The recursive-descent parser imposes no nesting limit, exhausting the C stack before resolveLocal calls bcmp with an invalid name pointer. Exploitation requires a low-privileged local user to supply source to an application embedding Wren; the demonstrated consequence is process termination under AddressSanitizer.
The record
- CVE
- CVE-2026-3385
- Published
- Mar 1, 2026
- Updated
- Mar 1, 2026
- Vendor
- wren-lang
- Product
- Wren
- Classifications
- CWE-674, CWE-404, T1499.004
- 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=0.1
- Affected versionversion=0.2
- Affected versionversion=0.3
- Affected versionversion=0.4.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
- Wren resolveLocal crashing source 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