Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

risc0-ethereum-contracts

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 1.7crates.ioPublished

    RISC Zero Ethereum invalid commitment with digest value of zero accepted by Steel.validateCommitment

    CVE-2025-52884 · GHSA-gjv3-89hh-9xq2

    Affected
    • crates.io risc0-ethereum-contracts < 2.1.1
    Fixed in
    2.1.1· Vendor fix available
    Issue
    Impact Prior to 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. Leveraging this bug to compromise the soundness of an application 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 (e.g. having the guest commit to a digest of zero, or failing to check the zkVM proof). Because this bug does not risk application integrity, correctly written applications are not at risk. Fix Please see [#605] for a full description of the bug, and the fix. This fix has been released as part of risc0-ethereum…

    Recommended action: Upgrade to 2.1.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →