https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 03:17:53 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-249115 EUVD-2026-249115 https://cve.radiocsirt.org/vuln/euvd-2026-249115 https://cve.radiocsirt.org/vuln/fkie_cve-2025-54873 <p>RISC Zero is a zero-knowledge verifiable general computing platform based on zk-STARKs and the RISC-V microarchitecture. RISC packages risc0-zkvm versions 2.0.0 through 2.1.0 and risc0-circuit-rv32im and risc0-circuit-rv32im-sys versions 2.0.0 through 2.0.4 contain vulnerabilities where signed integer division allows multiple outputs for certain inputs with only one being valid, and division by zero results are underconstrained. This issue is fixed in risc0-zkvm version 2.2.0 and version 3.0.0 for the risc0-circuit-rv32im and risc0-circuit-rv32im-sys packages.</p> <p>RISC Zero is a zero-knowledge verifiable general computing platform based on zk-STARKs and the RISC-V microarchitecture. RISC packages risc0-zkvm versions 2.0.0 through 2.1.0 and risc0-circuit-rv32im and risc0-circuit-rv32im-sys versions 2.0.0 through 2.0.4 contain vulnerabilities where signed integer division allows multiple outputs for certain inputs with only one being valid, and division by zero results are underconstrained. This issue is fixed in risc0-zkvm version 2.2.0 and version 3.0.0 for the risc0-circuit-rv32im and risc0-circuit-rv32im-sys packages.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-54873 https://cve.radiocsirt.org/vuln/ghsa-f6rc-24x4-ppxp <p><strong>Affected:</strong> crates.io: risc0-zkvm, crates.io: risc0-circuit-rv32im, crates.io: risc0-circuit-rv32im-sys</p> <p>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.</p> <p>This vulnerability was identified using the Picus tool from Veridise.</p> <p>Impacted on-chain verifiers have already been disabled via the estop mechanism outlined in the [Verifier Management Design](https://github.com/risc0/risc0-ethereum/blob/release-2.0/contracts/version-management-design.md#base-verifier-implementations).</p> <p>## Mitigation</p> <p>We recommend all impacted users upgrade as soon as possible.</p> <p>Rust applications using the `risc0-zkvm` crate at versions &lt; 2.2 should upgrade to version 2.2.0 or later.</p> <p>Smart contract applications using the official [RISC Zero Verifier Router](https://dev.risczero.com/api/blockchain-integration/contracts/verifier#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.</p> <p>Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.2 version of the verifier.</p> <p><strong>Affected:</strong> crates.io: risc0-zkvm, crates.io: risc0-circuit-rv32im, crates.io: risc0-circuit-rv32im-sys</p> <p>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.</p> <p>This vulnerability was identified using the Picus tool from Veridise.</p> <p>Impacted on-chain verifiers have already been disabled via the estop mechanism outlined in the [Verifier Management Design](https://github.com/risc0/risc0-ethereum/blob/release-2.0/contracts/version-management-design.md#base-verifier-implementations).</p> <p>## Mitigation</p> <p>We recommend all impacted users upgrade as soon as possible.</p> <p>Rust applications using the `risc0-zkvm` crate at versions &lt; 2.2 should upgrade to version 2.2.0 or later.</p> <p>Smart contract applications using the official [RISC Zero Verifier Router](https://dev.risczero.com/api/blockchain-integration/contracts/verifier#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.</p> <p>Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.2 version of the verifier.</p> https://cve.radiocsirt.org/vuln/ghsa-f6rc-24x4-ppxp