CVE-2025-52884 risc0-ethereum-contracts allows invalid commitment with digest value of zero to be accepted by Steel.validateCommitment
Attackers can bypass commitment validation in Steel library by using a zero digest, potentially compromising zkVM proof soundness if not paired with proper verification.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-52884?
CVE-2025-52884 is a low-severity vulnerability in risc0-ethereum, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
RISC Zero is a zero-knowledge verifiable general computing platform, with Ethereum integration. The risc0-ethereum repository contains Solidity verifier contracts, Steel EVM view call library, and supporting code. Prior to versions 2.1.1 and 2.2.0, the `Steel.validateCommitment` Solidity library function will return `true` for a crafted commitment with a digest value of zero. This violates the semantics of `validateCommitment`, as this does not commitment to a block that is in the current chain. Because the digest is zero, it does not correspond to any block and there exist no known openings. As a result, this commitment will never be produced by a correct zkVM guest using Steel and leveraging this bug to compromise the soundness of a program using Steel would require a separate bug or misuse of the Steel library, which is expected to be used to validate the root of state opening proofs. A fix has been released as part of `risc0-ethereum` 2.1.1 and 2.2.0. Users for the `Steel` Solidity library versions 2.1.0 or earlier should ensure they are using `Steel.validateCommitment` in tandem with zkVM proof verification of a Steel program, as shown in the ERC-20 counter example, and documentation. This is the correct usage of Steel, and users following this pattern are not at risk, and do not need to take action. Users not verifying a zkVM proof of a Steel program should update their application to do so, as this is incorrect usage of Steel.
Weakness: CWE-159
Which versions are affected by CVE-2025-52884?
2 open source packages ship an affected version, including risc0-ethereum-contracts.
| Package | Affected | Fixed in |
|---|---|---|
risc0-ethereum-contracts crates.io | All versions | 2.1.1 |
risc0-ethereum-contracts crates.io | All versions | 2.1.1 |
How do I fix CVE-2025-52884?
Upgrade risc0-ethereum-contracts to 2.1.1 or later.
Is CVE-2025-52884 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52884 exists.
Sources
Also known as GHSA-gjv3-89hh-9xq2.