How severe is CVE-2025-52884?

No CVSS score has been assigned to CVE-2025-52884 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-52884?

CVE-2025-52884 affects the following packages: risc0-ethereum-contracts (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2025-52884?

Update risc0-ethereum-contracts to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-52884 is resolved across your whole dependency graph.

How do I detect CVE-2025-52884 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for risc0-ethereum-contracts, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-52884 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-52884?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-52884 can be triaged on real exposure rather than presence alone.

Is CVE-2025-52884 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-52884 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-52884?

CVE-2025-52884 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-52884?

CVE-2025-52884 is classified as CWE-159 (CWE-159). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-52884 published, and has it been updated?

CVE-2025-52884 was published on June 24, 2025 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

CVE-2025-52884 — risc0-ethereum-contracts

Fix: risc0/risc0-ethereum@3bbac85

CVE-2025-52884 is a CWE-159 vulnerability in risc0-ethereum-contracts. A fix is available for risc0-ethereum-contracts — see the affected versions and patch details below.

risc0-ethereum-contracts allows invalid commitment with digest value of zero to be accepted by Steel.validateCommitment

Also known asGHSA-gjv3-89hh-9xq2

Published

Jun 24, 2025

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-52884.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🦀risc0-ethereum-contracts

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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 2.1.1 and 2.2.0.

Recommended actions

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.

Credit

A thank you to Daniel526 on HackenProof for reporting this issue

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`risc0-ethereum-contracts`	all versions	2.1.1`cargo update -p risc0-ethereum-contracts --precise 2.1.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for risc0-ethereum-contracts, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update risc0-ethereum-contracts to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-52884 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-52884 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-52884. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 t

O3 Security · Impact-Aware SCA

Is CVE-2025-52884 in your dependencies?

O3 Security finds CVE-2025-52884 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works