CVE-2025-52884: risc0-ethereum · Improper Handling of Invalid Use of Special Elements
Affects risc0-ethereumSource CVE Database V5
Not known to be exploited · CVSS 1.7 Low : upgrade to 2.1.1 when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.1.1
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade risc0/risc0-ethereum to 2.1.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubrisc0/risc0-ethereumpkg:github/risc0/risc0-ethereumOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Upgrade risc0-ethereum Steel Solidity library to version 2.1.1 or later to incorporate the official fix.
- Ensure that all applications using Steel.validateCommitment also perform zkVM proof verification of Steel programs as per the recommended usage pattern, referencing the ERC-20 counter example and official documentation.
- Conduct code audits to verify that no application logic relies solely on validateCommitment without zkVM proof verification.
- Implement automated testing to detect any acceptance of zero digest commitments to prevent misuse.
- Educate development teams on correct usage patterns of zero-knowledge proof libraries to avoid misuse that could lead to soundness compromises.
- Monitor risc0-ethereum project updates and community advisories for any related vulnerabilities or best practices.
- For organizations deploying smart contracts in production, consider additional external audits focusing on zero-knowledge proof validation logic to ensure robustness against similar issues.
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.
References
- github.com/risc0/risc0-ethereum/security/advisories/GHSA-gjv3-89hh-9xq2 (opens in a new tab)
- github.com/risc0/risc0-ethereum/pull/605 (opens in a new tab)
- github.com/risc0/risc0-ethereum/commit/3bbac859c7132b21ba5fdf2d47f1dd52e7e73d98 (opens in a new tab)
- docs.beboundless.xyz/developers/steel/how-it-works (opens in a new tab)
- github.com/risc0/risc0-ethereum/blob/ff0cb9253a87945b653b825711b8b5075f8b7545/examples/erc20-counter/contracts/src/Counter.sol (opens in a new tab)
- github.com/risc0/risc0-ethereum/releases/tag/v2.1.1 (opens in a new tab)
- github.com/risc0/risc0-ethereum/releases/tag/v2.2.0 (opens in a new tab)