risc0-circuit-rv32im
Activity
- Latest release
- 1mo ago
- Total releases
- 86
- Cadence
- ~8 days
- Last 12 months
- 4
Details
- License
- Apache-2.0
- First release
- Dec 03, 2022
| Version | Released | |
|---|---|---|
4.0.5
unknown
|
4.0.5
unknown
Dependencies (31)
+ 23 more |
|
4.0.4
unknown
|
4.0.4
unknown
Dependencies (31)
+ 23 more |
|
5.0.0-rc.1
unknown
|
5.0.0-rc.1
unknown
Dependencies (33)
+ 25 more |
|
4.0.3
unknown
|
4.0.3
unknown
Dependencies (31)
+ 23 more |
|
4.0.2
unknown
|
4.0.2
unknown
Dependencies (31)
+ 23 more |
|
3.0.1
unknown
|
3.0.1
unknown
Dependencies (29)
+ 21 more |
|
4.0.1
unknown
|
4.0.1
unknown
Dependencies (31)
+ 23 more |
|
4.0.0
unknown
yanked
|
4.0.0
unknown
yanked
Dependencies (31)
+ 23 more |
|
4.0.0-rc.3
unknown
|
4.0.0-rc.3
unknown
Dependencies (31)
+ 23 more |
|
4.0.0-rc.2
unknown
|
4.0.0-rc.2
unknown
Dependencies (31)
+ 23 more |
|
3.0.0
unknown
|
3.0.0
unknown
Dependencies (29)
+ 21 more |
|
2.0.4
unknown
yanked
1 CVE
CVE-2025-54873
GHSA-f6rc-24x4-ppxp
Aug 05, 2025
RISC Zero Underconstrained Vulnerability: Division
Low
Network
Low
None
None
Two issues were found: For some inputs to signed integer division, the circuit allowed two outputs, only one of which was valid. Additionally, the result of division by zero was underconstrained. This vulnerability was identified using the Picus tool from Veridise. Impacted on-chain verifiers have already been disabled via the estop mechanism outlined in the Verifier Management Design. MitigationWe recommend all impacted users upgrade as soon as possible. Rust applications using the Smart contract applications using the official RISC Zero Verifier Router do not need to take any action: zkVM version 2.2 is active on all official routers, and version 2.1 has been disabled. Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.2 version of the verifier. Fixed in
3.0.0
References Updated Aug 06, 2025 · Source: OSV.dev |
2.0.4
unknown
yanked
Dependencies (29)
+ 21 more |
|
3.0.0-rc.1
unknown
1 CVE
CVE-2025-54873
GHSA-f6rc-24x4-ppxp
Aug 05, 2025
RISC Zero Underconstrained Vulnerability: Division
Low
Network
Low
None
None
Two issues were found: For some inputs to signed integer division, the circuit allowed two outputs, only one of which was valid. Additionally, the result of division by zero was underconstrained. This vulnerability was identified using the Picus tool from Veridise. Impacted on-chain verifiers have already been disabled via the estop mechanism outlined in the Verifier Management Design. MitigationWe recommend all impacted users upgrade as soon as possible. Rust applications using the Smart contract applications using the official RISC Zero Verifier Router do not need to take any action: zkVM version 2.2 is active on all official routers, and version 2.1 has been disabled. Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.2 version of the verifier. Fixed in
3.0.0
References Updated Aug 06, 2025 · Source: OSV.dev |
3.0.0-rc.1
unknown
Dependencies (29)
+ 21 more |
|
2.0.3
unknown
yanked
2 CVEs
CVE-2025-54873
GHSA-f6rc-24x4-ppxp
Aug 05, 2025
RISC Zero Underconstrained Vulnerability: Division
Low
Network
Low
None
None
Two issues were found: For some inputs to signed integer division, the circuit allowed two outputs, only one of which was valid. Additionally, the result of division by zero was underconstrained. This vulnerability was identified using the Picus tool from Veridise. Impacted on-chain verifiers have already been disabled via the estop mechanism outlined in the Verifier Management Design. MitigationWe recommend all impacted users upgrade as soon as possible. Rust applications using the Smart contract applications using the official RISC Zero Verifier Router do not need to take any action: zkVM version 2.2 is active on all official routers, and version 2.1 has been disabled. Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.2 version of the verifier. Fixed in
3.0.0
References Updated Aug 06, 2025 · Source: OSV.dev
CVE-2025-52484
GHSA-g3qg-6746-3mg9
Jun 20, 2025
zkVM Underconstrained Vulnerability
Low
Network
Low
None
None
Due to a missing constraint in the rv32im circuit, any 3-register RISC-V instruction (including remu and divu) in risc0-zkvm 2.0.0, 2.0.1, and 2.0.2 are vulnerable to an attack by a malicious prover. The main idea for the attack is to confuse the RISC-V virtual machine into treating the value of the rs1 register as the same as the rs2 register due to a lack of constraints in the rv32im circuit. This vulnerability was reported by Christoph Hochrainer via our Hackenproof bug bounty. We have evaluated the severity of the vulnerability as “Critical,” and paid a bounty. The fix for the circuit was implemented in zirgen/pull/238, and the update to risc0 was implemented in risc0/pull/3181. Impacted on-chain verifiers have already been disabled via the estop mechanism outlined in the Verifier Management Design. MitigationWe recommend all impacted users upgrade as soon as possible. Rust applications using the risc0-zkvm crate at versions 2.0.0, 2.0.1, and 2.0.2 should upgrade to version 2.1.0. Smart contract applications using the official RISC Zero Verifier Router do not need to take any action: zkVM version 2.1 is active on all official routers, and version 2.0 has been disabled. Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.1 version of the verifier. Fixed in
2.0.4
References
Updated Jun 27, 2025 · Source: OSV.dev |
2.0.3
unknown
yanked
Dependencies (29)
+ 21 more |
|
2.0.2
unknown
yanked
2 CVEs
CVE-2025-54873
GHSA-f6rc-24x4-ppxp
Aug 05, 2025
RISC Zero Underconstrained Vulnerability: Division
Low
Network
Low
None
None
Two issues were found: For some inputs to signed integer division, the circuit allowed two outputs, only one of which was valid. Additionally, the result of division by zero was underconstrained. This vulnerability was identified using the Picus tool from Veridise. Impacted on-chain verifiers have already been disabled via the estop mechanism outlined in the Verifier Management Design. MitigationWe recommend all impacted users upgrade as soon as possible. Rust applications using the Smart contract applications using the official RISC Zero Verifier Router do not need to take any action: zkVM version 2.2 is active on all official routers, and version 2.1 has been disabled. Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.2 version of the verifier. Fixed in
3.0.0
References Updated Aug 06, 2025 · Source: OSV.dev
CVE-2025-52484
GHSA-g3qg-6746-3mg9
Jun 20, 2025
zkVM Underconstrained Vulnerability
Low
Network
Low
None
None
Due to a missing constraint in the rv32im circuit, any 3-register RISC-V instruction (including remu and divu) in risc0-zkvm 2.0.0, 2.0.1, and 2.0.2 are vulnerable to an attack by a malicious prover. The main idea for the attack is to confuse the RISC-V virtual machine into treating the value of the rs1 register as the same as the rs2 register due to a lack of constraints in the rv32im circuit. This vulnerability was reported by Christoph Hochrainer via our Hackenproof bug bounty. We have evaluated the severity of the vulnerability as “Critical,” and paid a bounty. The fix for the circuit was implemented in zirgen/pull/238, and the update to risc0 was implemented in risc0/pull/3181. Impacted on-chain verifiers have already been disabled via the estop mechanism outlined in the Verifier Management Design. MitigationWe recommend all impacted users upgrade as soon as possible. Rust applications using the risc0-zkvm crate at versions 2.0.0, 2.0.1, and 2.0.2 should upgrade to version 2.1.0. Smart contract applications using the official RISC Zero Verifier Router do not need to take any action: zkVM version 2.1 is active on all official routers, and version 2.0 has been disabled. Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.1 version of the verifier. Fixed in
2.0.4
References
Updated Jun 27, 2025 · Source: OSV.dev |
2.0.2
unknown
yanked
Dependencies (29)
+ 21 more |
|
1.2.6
unknown
|
1.2.6
unknown
Dependencies (27)
+ 19 more |
|
2.0.1
unknown
yanked
2 CVEs
CVE-2025-54873
GHSA-f6rc-24x4-ppxp
Aug 05, 2025
RISC Zero Underconstrained Vulnerability: Division
Low
Network
Low
None
None
Two issues were found: For some inputs to signed integer division, the circuit allowed two outputs, only one of which was valid. Additionally, the result of division by zero was underconstrained. This vulnerability was identified using the Picus tool from Veridise. Impacted on-chain verifiers have already been disabled via the estop mechanism outlined in the Verifier Management Design. MitigationWe recommend all impacted users upgrade as soon as possible. Rust applications using the Smart contract applications using the official RISC Zero Verifier Router do not need to take any action: zkVM version 2.2 is active on all official routers, and version 2.1 has been disabled. Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.2 version of the verifier. Fixed in
3.0.0
References Updated Aug 06, 2025 · Source: OSV.dev
CVE-2025-52484
GHSA-g3qg-6746-3mg9
Jun 20, 2025
zkVM Underconstrained Vulnerability
Low
Network
Low
None
None
Due to a missing constraint in the rv32im circuit, any 3-register RISC-V instruction (including remu and divu) in risc0-zkvm 2.0.0, 2.0.1, and 2.0.2 are vulnerable to an attack by a malicious prover. The main idea for the attack is to confuse the RISC-V virtual machine into treating the value of the rs1 register as the same as the rs2 register due to a lack of constraints in the rv32im circuit. This vulnerability was reported by Christoph Hochrainer via our Hackenproof bug bounty. We have evaluated the severity of the vulnerability as “Critical,” and paid a bounty. The fix for the circuit was implemented in zirgen/pull/238, and the update to risc0 was implemented in risc0/pull/3181. Impacted on-chain verifiers have already been disabled via the estop mechanism outlined in the Verifier Management Design. MitigationWe recommend all impacted users upgrade as soon as possible. Rust applications using the risc0-zkvm crate at versions 2.0.0, 2.0.1, and 2.0.2 should upgrade to version 2.1.0. Smart contract applications using the official RISC Zero Verifier Router do not need to take any action: zkVM version 2.1 is active on all official routers, and version 2.0 has been disabled. Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.1 version of the verifier. Fixed in
2.0.4
References
Updated Jun 27, 2025 · Source: OSV.dev |
2.0.1
unknown
yanked
Dependencies (29)
+ 21 more |
|
2.0.0-rc.3
unknown
|
2.0.0-rc.3
unknown
Dependencies (29)
+ 21 more |
|
2.0.0-rc.2
unknown
|
2.0.0-rc.2
unknown
Dependencies (28)
+ 20 more |
|
2.0.0
unknown
yanked
2 CVEs
CVE-2025-54873
GHSA-f6rc-24x4-ppxp
Aug 05, 2025
RISC Zero Underconstrained Vulnerability: Division
Low
Network
Low
None
None
Two issues were found: For some inputs to signed integer division, the circuit allowed two outputs, only one of which was valid. Additionally, the result of division by zero was underconstrained. This vulnerability was identified using the Picus tool from Veridise. Impacted on-chain verifiers have already been disabled via the estop mechanism outlined in the Verifier Management Design. MitigationWe recommend all impacted users upgrade as soon as possible. Rust applications using the Smart contract applications using the official RISC Zero Verifier Router do not need to take any action: zkVM version 2.2 is active on all official routers, and version 2.1 has been disabled. Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.2 version of the verifier. Fixed in
3.0.0
References Updated Aug 06, 2025 · Source: OSV.dev
CVE-2025-52484
GHSA-g3qg-6746-3mg9
Jun 20, 2025
zkVM Underconstrained Vulnerability
Low
Network
Low
None
None
Due to a missing constraint in the rv32im circuit, any 3-register RISC-V instruction (including remu and divu) in risc0-zkvm 2.0.0, 2.0.1, and 2.0.2 are vulnerable to an attack by a malicious prover. The main idea for the attack is to confuse the RISC-V virtual machine into treating the value of the rs1 register as the same as the rs2 register due to a lack of constraints in the rv32im circuit. This vulnerability was reported by Christoph Hochrainer via our Hackenproof bug bounty. We have evaluated the severity of the vulnerability as “Critical,” and paid a bounty. The fix for the circuit was implemented in zirgen/pull/238, and the update to risc0 was implemented in risc0/pull/3181. Impacted on-chain verifiers have already been disabled via the estop mechanism outlined in the Verifier Management Design. MitigationWe recommend all impacted users upgrade as soon as possible. Rust applications using the risc0-zkvm crate at versions 2.0.0, 2.0.1, and 2.0.2 should upgrade to version 2.1.0. Smart contract applications using the official RISC Zero Verifier Router do not need to take any action: zkVM version 2.1 is active on all official routers, and version 2.0 has been disabled. Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.1 version of the verifier. Fixed in
2.0.4
References
Updated Jun 27, 2025 · Source: OSV.dev |
2.0.0
unknown
yanked
Dependencies (28)
+ 20 more |
|
2.0.0-rc.1
unknown
|
2.0.0-rc.1
unknown
Dependencies (27)
+ 19 more |
|
1.2.5
unknown
|
1.2.5
unknown
Dependencies (27)
+ 19 more |
|
1.1.4
unknown
|
1.1.4
unknown
Dependencies (21)
+ 13 more |
|
1.3.0
unknown
yanked
|
1.3.0
unknown
yanked
Dependencies (28)
+ 20 more |
|
1.2.4
unknown
|
1.2.4
unknown
Dependencies (27)
+ 19 more |
|
1.3.0-rc.1
unknown
|
1.3.0-rc.1
unknown
Dependencies (28)
+ 20 more |
|
1.2.3
unknown
|
1.2.3
unknown
Dependencies (27)
+ 19 more |
|
1.2.2
unknown
|
1.2.2
unknown
Dependencies (27)
+ 19 more |
|
1.2.1
unknown
|
1.2.1
unknown
Dependencies (27)
+ 19 more |
|
1.2.1-rc.1
unknown
|
1.2.1-rc.1
unknown
Dependencies (27)
+ 19 more |
|
1.2.1-rc.0
unknown
|
1.2.1-rc.0
unknown
Dependencies (26)
+ 18 more |
|
1.2.0
unknown
|
1.2.0
unknown
Dependencies (26)
+ 18 more |
|
1.2.0-rc.2
unknown
|
1.2.0-rc.2
unknown
Dependencies (26)
+ 18 more |
|
1.2.0-rc.1
unknown
|
1.2.0-rc.1
unknown
Dependencies (26)
+ 18 more |
|
1.1.3
unknown
|
1.1.3
unknown
Dependencies (21)
+ 13 more |
|
1.1.2
unknown
|
1.1.2
unknown
Dependencies (21)
+ 13 more |
|
1.1.1
unknown
|
1.1.1
unknown
Dependencies (21)
+ 13 more |
|
1.1.0
unknown
yanked
|
1.1.0
unknown
yanked
Dependencies (21)
+ 13 more |
|
1.1.0-rc.3
unknown
|
1.1.0-rc.3
unknown
Dependencies (21)
+ 13 more |
|
1.1.0-rc.2
unknown
|
1.1.0-rc.2
unknown
Dependencies (21)
+ 13 more |
|
1.1.0-rc.1
unknown
|
1.1.0-rc.1
unknown
Dependencies (22)
+ 14 more |
|
1.0.5
unknown
|
1.0.5
unknown
Dependencies (22)
+ 14 more |
|
1.0.4
unknown
|
1.0.4
unknown
Dependencies (22)
+ 14 more |
|
1.0.3
unknown
|
1.0.3
unknown
Dependencies (22)
+ 14 more |
|
1.0.2
unknown
|
1.0.2
unknown
Dependencies (22)
+ 14 more |
|
1.0.1
unknown
|
1.0.1
unknown
Dependencies (22)
+ 14 more |
|
1.0.0
unknown
|
1.0.0
unknown
Dependencies (22)
+ 14 more |
|
1.0.0-rc.7
unknown
|
1.0.0-rc.7
unknown
Dependencies (22)
+ 14 more |
|
1.0.0-rc.6
unknown
|
1.0.0-rc.6
unknown
Dependencies (22)
+ 14 more |
|
1.0.0-rc.5
unknown
|
1.0.0-rc.5
unknown
Dependencies (22)
+ 14 more |