Heap corruption via re-entrant iterator double release
Published Mar 12, 2026 · Updated Mar 12, 2026
Use-after-free in QuickJS-NG QuickJS 0.12.0 through 0.12.1 allows local users to corrupt heap memory via crafted JavaScript. Within js_iterator_concat_next, user-controlled @@iterator code can re-enter return() before the running guard is set, freeing values that execution later releases again. Low-privileged local code execution is required; the demonstrated consequence is a heap-use-after-free and process abort, while broader code-execution impact is unproven.
Summary
What happened
Use-after-free in QuickJS-NG QuickJS 0.12.0 through 0.12.1 allows local users to corrupt heap memory via crafted JavaScript. Within js_iterator_concat_next, user-controlled @@iterator code can re-enter return() before the running guard is set, freeing values that execution later releases again. Low-privileged local code execution is required; the demonstrated consequence is a heap-use-after-free and process abort, while broader code-execution impact is unproven.
The record
- CVE
- CVE-2026-3979
- Published
- Mar 12, 2026
- Updated
- Mar 12, 2026
- Vendor
- QuickJS-NG
- Product
- QuickJS
- Classifications
- CWE-119, CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 12, 2026CVE publishedPublication date reported by the CVE source.
- Mar 12, 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.12.0
- Affected versionversion=0.12.1
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
- Iterator.concat re-entrancy 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