GHSA-f6rc-24x4-ppxp — risc0-zkvm
Fix: risc0/risc0#3235GHSA-f6rc-24x4-ppxp 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
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 GHSA-f6rc-24x4-ppxp.
EPSS Exploitation Probability
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
risc0-zkvm🦀risc0-circuit-rv32im🦀risc0-circuit-rv32im-sysReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | risc0-zkvm | ≥ 2.0.0&&< 2.2.0 | 2.2.0cargo update -p risc0-zkvm --precise 2.2.0 |
| 🦀crates.io | risc0-circuit-rv32im | ≥ 2.0.0&&< 3.0.0 | 3.0.0cargo update -p risc0-circuit-rv32im --precise 3.0.0 |
| 🦀crates.io | risc0-circuit-rv32im-sys | ≥ 2.0.0&&< 3.0.0 | 3.0.0cargo update -p risc0-circuit-rv32im-sys --precise 3.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
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 GHSA-f6rc-24x4-ppxp 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 GHSA-f6rc-24x4-ppxp can be triaged on real exposure rather than presence alone.
Tailored to GHSA-f6rc-24x4-ppxp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-f6rc-24x4-ppxp in your dependencies?
O3 Security finds GHSA-f6rc-24x4-ppxp across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.