Advisory

GHSA-jqq4-c7wq-36h7

Also known as: CVE-2025-61588

Summary

risc0 vulnerable to arbitrary code execution in guest via memory safety failure in sys_read

Details

Arbitrary code execution in guest via memory safety failure in sys_read

In affected versions of risc0-zkvm-platform, when the zkVM guest calls sys_read, the host is able to use a crafted response to write to an arbitrary memory location in the guest. This capability can be leveraged to execute arbitrary code within the guest. As sys_read is the mechanism by which input is requested by the guest, all guest programs built with the affected versions are vulnerable. This critically compromises the soundness guarantees of the guest program.

A fix was applied in \#3351. The vulnerable pointer arithmetic was removed, and replaced with a simplified implementation in the v1compat kernel which uses Rust’s slice functions to guarantee memory safety.

The fix has been released as part of risc0-zkvm versions 2.3.2 and 3.0.3. All prior versions are affected.

Remediation

All developers of zkVM applications should update their guests to use risc0-zkvm versions ^2.3.2 or ^3.0.3.

This upgrade can be accomplished by editing all Cargo.toml files in the following way.

  • Any references to `risc0-zkvm` should use version specifiers ”2.3.2” or ”3.0.3”.
  • Any references to `risc0-build` should use version specifiers ”2.3.2” or ”3.0.3”, matching risc0-zkvm.
  • Any references to `risc0-zkvm-platform` should use version specifier ”2.1.0” or later. Most projects will not have direct references to this crate.

Rebuild your application including the guest. You can run the following command to check that the patch is applied:

# Provide the path to your guest Cargo.toml. Should report risc0-zkvm-platform >=v2.1.0
cargo tree --depth 0 -p risc0-zkvm-platform --manifest-path path/to/methods/guest/Cargo.toml

Any applications that use the image ID of this guest need to be updated with the newly built image ID.

Note that there are no changes to the RISC Zero proof system or circuits. Provers are not required to take any action. Users of the Groth16 smart contract verifier and the RISC Zero Verifier Router are not required to take any action beyond updating their guest programs.

Any applications using the risc0-aggregation crate or the RiscZeroSetVerifier smart contract should update to version >=0.9. This application includes a zkVM guest, which is vulnerable in versions prior to 0.9. Instances of the RiscZeroSetVerifier operated by RISC Zero have been disabled via the estop mechanism outlined in the Verifier Management Design.

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2025-10-01 21:04 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

risc0-zkvm-platform

crates.io · All systems

Affected

  • introduced 0, fixed 2.1.0 (semver)

Fixed versions

2.1.0

Fix

  • Fixed version 2.1.0
    cargo update -p risc0-zkvm-platform --precise 2.1.0

risc0-zkos-v1compat

crates.io · All systems

Affected

  • introduced 0, fixed 2.1.0 (semver)

Fixed versions

2.1.0

Fix

  • Fixed version 2.1.0
    cargo update -p risc0-zkos-v1compat --precise 2.1.0

risc0-aggregation

crates.io · All systems

Affected

  • introduced 0, fixed 0.9 (ecosystem)

Fixed versions

0.9

Fix

  • Fixed version 0.9
    cargo update -p risc0-aggregation --precise 0.9

risc0-zkvm

crates.io · All systems

Affected

  • introduced 0, fixed 2.3.2 (semver)

Fixed versions

2.3.2

Fix

  • Fixed version 2.3.2
    cargo update -p risc0-zkvm --precise 2.3.2

risc0-zkvm

crates.io · All systems

Affected

  • introduced 3.0.0, fixed 3.0.3 (semver)

Fixed versions

3.0.3

Fix

  • Fixed version 3.0.3
    cargo update -p risc0-zkvm --precise 3.0.3

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences