Heap corruption via nested-array result under-allocation
Published Apr 23, 2026 · Updated Apr 23, 2026
Heap corruption in Noir before 1.0.0-beta.19 allows attackers to overwrite adjacent Brillig VM memory via crafted foreign-call results. allocate_foreign_call_result_array uses a nested array's logical element count without multiplying by composite element width, so the VM reserves too few heap slots. Exploitation requires a foreign call returning nested arrays of tuples or other composite values, after which result metadata and values overwrite neighboring memory.
Summary
What happened
Heap corruption in Noir before 1.0.0-beta.19 allows attackers to overwrite adjacent Brillig VM memory via crafted foreign-call results. allocate_foreign_call_result_array uses a nested array's logical element count without multiplying by composite element width, so the VM reserves too few heap slots. Exploitation requires a foreign call returning nested arrays of tuples or other composite values, after which result metadata and values overwrite neighboring memory.
The record
- CVE
- CVE-2026-41197
- Published
- Apr 23, 2026
- Updated
- Apr 23, 2026
- Vendor
- Noir Lang
- Product
- Noir
- Classifications
- CWE-131
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 23, 2026CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=< 1.0.0-beta.19
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
No public exploit references are available in this record.
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