# CVE-2025-54873: RISC Zero Underconstrained Vulnerability: Division

> Attackers can exploit underconstrained division logic in RISC Zero to generate invalid proofs, bypassing verification integrity.

- **Severity:** Low 2.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Aug 2025
- **Updated:** 6 Aug 2025
- **Also known as:** GHSA-f6rc-24x4-ppxp

## What is CVE-2025-54873?

CVE-2025-54873 is a low-severity vulnerability in risc0, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RISC Zero is a zero-knowledge verifiable general computing platform based on zk-STARKs and the RISC-V microarchitecture. RISC packages risc0-zkvm versions 2.0.0 through 2.1.0 and risc0-circuit-rv32im and risc0-circuit-rv32im-sys versions 2.0.0 through 2.0.4 contain vulnerabilities where signed integer division allows multiple outputs for certain inputs with only one being valid, and division by zero results are underconstrained. This issue is fixed in risc0-zkvm version 2.2.0 and version 3.0.0 for the  risc0-circuit-rv32im and risc0-circuit-rv32im-sys packages.

Weakness: CWE-369 (Divide By Zero)

## Which versions are affected by CVE-2025-54873?

6 open source packages ship an affected version, including risc0-circuit-rv32im, risc0-circuit-rv32im-sys and risc0-zkvm.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `risc0-circuit-rv32im` | crates.io | From 2.0.0 | 3.0.0 |
| `risc0-circuit-rv32im` | crates.io | From 2.0.0 | 3.0.0 |
| `risc0-circuit-rv32im-sys` | crates.io | From 2.0.0 | 3.0.0 |
| `risc0-circuit-rv32im-sys` | crates.io | From 2.0.0 | 3.0.0 |
| `risc0-zkvm` | crates.io | From 2.0.0 | 2.2.0 |
| `risc0-zkvm` | crates.io | From 2.0.0 | 2.2.0 |

## How do I fix CVE-2025-54873?

Upgrade risc0-circuit-rv32im to 3.0.0 or later.

## Is CVE-2025-54873 being exploited?

There is no known exploitation of CVE-2025-54873 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54873 and fix it if it is affected.

What it is: CVE-2025-54873 is a low-severity vulnerability in risc0, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54873 in the wild and no public exploit code.

Affected packages and fixed versions:
- risc0-circuit-rv32im (crates.io): affected from 2.0.0; fixed in 3.0.0
- risc0-circuit-rv32im (crates.io): affected from 2.0.0; fixed in 3.0.0
- risc0-circuit-rv32im-sys (crates.io): affected from 2.0.0; fixed in 3.0.0
- risc0-circuit-rv32im-sys (crates.io): affected from 2.0.0; fixed in 3.0.0
- risc0-zkvm (crates.io): affected from 2.0.0; fixed in 2.2.0
- risc0-zkvm (crates.io): affected from 2.0.0; fixed in 2.2.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-54873/ (Markdown: https://insights.sbomify.com/CVE-2025-54873/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54873
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54873
- OSV: https://osv.dev/vulnerability/CVE-2025-54873

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-54873/
Summaries are generated and may contain mistakes; the official description above is the record.