How severe is CVE-2025-54873?

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

Which packages are affected by CVE-2025-54873?

CVE-2025-54873 affects the following packages: risc0-zkvm (crates.io), risc0-circuit-rv32im (crates.io), risc0-circuit-rv32im-sys (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2025-54873?

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

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

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

How do I mitigate CVE-2025-54873 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.

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

No public exploit code has been indexed for CVE-2025-54873 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-54873?

CVE-2025-54873 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th 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-54873?

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

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

CVE-2025-54873 was published on August 5, 2025 and was last updated on October 28, 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-54873 — risc0-zkvm

Fix: risc0/risc0#3235

CVE-2025-54873 is a CWE-369 vulnerability in risc0-zkvm. A fix is available for risc0-zkvm — see the affected versions and patch details below.

RISC Zero Underconstrained Vulnerability: Division

Also known asGHSA-f6rc-24x4-ppxp

Published

Aug 5, 2025

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

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

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.04%

Lower risk than most CVEs35th percentile — riskier than 35% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

🦀risc0-zkvm🦀risc0-circuit-rv32im🦀risc0-circuit-rv32im-sys

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

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.

This vulnerability was identified using the Picus tool from Veridise.

Impacted on-chain verifiers have already been disabled via the estop mechanism outlined in the Verifier Management Design.

Mitigation

We recommend all impacted users upgrade as soon as possible.

Rust applications using the risc0-zkvm crate at versions < 2.2 should upgrade to version 2.2.0 or later.

Smart contract applications using the official RISC Zero 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.

Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.2 version of the verifier.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`risc0-zkvm`	≥ 2.0.0&&< 2.2.0	2.2.0`cargo update -p risc0-zkvm --precise 2.2.0`
🦀crates.io	`risc0-circuit-rv32im`	≥ 2.0.0&&< 3.0.0	3.0.0`cargo update -p risc0-circuit-rv32im --precise 3.0.0`
🦀crates.io	`risc0-circuit-rv32im-sys`	≥ 2.0.0&&< 3.0.0	3.0.0`cargo update -p risc0-circuit-rv32im-sys --precise 3.0.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for risc0-zkvm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update risc0-zkvm to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-54873 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.

Frequently Asked Questions

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. This vulnerability was identified using the Picus tool from Veridise. 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). ## Mitigation We recommend all impacted users upgrade as soon as possible.

O3 Security · Impact-Aware SCA

Is CVE-2025-54873 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works