Code execution via faulty MRET state restoration
Published Aug 19, 2026 · Updated Aug 19, 2026
Code execution in the BOOM BoomTile RTL benchmark 1.2 allows remote attackers to run arbitrary code through crafted MRET handling. The public record identifies CSR trap-return restoration, MRET handling, the mstatus.MPRV update path, and CSRFile as the faulty locus but does not disclose the precise erroneous operation. Exploitation requires user interaction and reaches the simulated processor logic in the ProcessorFuzz benchmark.
Summary
What happened
Code execution in the BOOM BoomTile RTL benchmark 1.2 allows remote attackers to run arbitrary code through crafted MRET handling. The public record identifies CSR trap-return restoration, MRET handling, the mstatus.MPRV update path, and CSRFile as the faulty locus but does not disclose the precise erroneous operation. Exploitation requires user interaction and reaches the simulated processor logic in the ProcessorFuzz benchmark.
The record
- CVE
- CVE-2026-71694
- Published
- Aug 19, 2026
- Updated
- Aug 19, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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