Local application crash via compiler null dereference
Published Mar 1, 2026 · Updated Mar 1, 2026
NULL pointer dereference in Wren 0.1 through 0.4.0 allows local users to crash an embedding application via a crafted script. When compiling the crafted nested for-loop script, getByteCountForArguments reads a struct field through a null pointer after endLoop calls it. The affected Wren VM must compile attacker-controlled source locally; exploitation interrupts the embedding process without reported data disclosure or code execution.
Summary
What happened
NULL pointer dereference in Wren 0.1 through 0.4.0 allows local users to crash an embedding application via a crafted script. When compiling the crafted nested for-loop script, getByteCountForArguments reads a struct field through a null pointer after endLoop calls it. The affected Wren VM must compile attacker-controlled source locally; exploitation interrupts the embedding process without reported data disclosure or code execution.
The record
- CVE
- CVE-2026-3387
- Published
- Mar 1, 2026
- Updated
- Mar 1, 2026
- Vendor
- wren-lang
- Product
- Wren
- Classifications
- CWE-404, CWE-476, 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?
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
- Wren getByteCountForArguments crash reproductionproof 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