Invalid proof acceptance via unconstrained register operands
Published Jun 20, 2025 · Updated Jun 23, 2025
Proof-verification failure in RISC Zero zkVM 2.0.0 through 2.0.2 allows remote attackers to obtain acceptance of invalid execution proofs. The rv32im circuit omits a constraint linking three-register instruction operands, allowing a prover to make rs1 and rs2 appear identical during verification. Reachability requires an application to accept proofs from an untrusted prover; official Verifier Router deployments had version 2.0 disabled.
Summary
What happened
Proof-verification failure in RISC Zero zkVM 2.0.0 through 2.0.2 allows remote attackers to obtain acceptance of invalid execution proofs. The rv32im circuit omits a constraint linking three-register instruction operands, allowing a prover to make rs1 and rs2 appear identical during verification. Reachability requires an application to accept proofs from an untrusted prover; official Verifier Router deployments had version 2.0 disabled.
The record
- CVE
- CVE-2025-52484
- Published
- Jun 20, 2025
- Updated
- Jun 23, 2025
- Vendor
- RISC Zero
- Product
- RISC Zero zkVM
- Classifications
- CWE-345
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 20, 2025CVE publishedPublication date reported by the CVE source.
- Jun 23, 2025Record 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=>= 2.0.0, < 2.1.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
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