How severe is GHSA-8m24-3cfx-9fjw?

No CVSS score has been assigned to GHSA-8m24-3cfx-9fjw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8m24-3cfx-9fjw?

GHSA-8m24-3cfx-9fjw affects the following packages: sp1-recursion-circuit (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-8m24-3cfx-9fjw?

Update sp1-recursion-circuit to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8m24-3cfx-9fjw is resolved across your whole dependency graph.

How do I detect GHSA-8m24-3cfx-9fjw in my crates.io dependencies?

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

How do I mitigate GHSA-8m24-3cfx-9fjw 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 GHSA-8m24-3cfx-9fjw actively exploited in the wild?

No public exploit code has been indexed for GHSA-8m24-3cfx-9fjw 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.

When was GHSA-8m24-3cfx-9fjw published, and has it been updated?

GHSA-8m24-3cfx-9fjw was published on November 8, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-8m24-3cfx-9fjw: sp1-recursion-circuit

Real-World Exposure

1 pkg affected

🦀sp1-recursion-circuit

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

During proof generation, the prover must observe all values sent to the verifier to generate valid Fiat-Shamir challenges. Prior to v3.0.0 the cumulative sum of the permutation argument was not observed when sampling zeta, which is a random challenge sampled to force the constraints to be true. In v3.0.0, this is fixed by observing the cumulative sum into the challenger, which can is done by observing the commit to the entire permutation trace.

While this vulnerability is theoretically present in v2.0.0 and below, exploiting it is quite a difficult task as the cumulative sum one can get from manipulation is essentially random. It requires practically infeasible amount of computation and deep knowledge of cryptographic attacks to carry out.

This issue was discovered during the audit of SP1 V3.0.0 and was officially fixed on October 17th. Out of abundance of caution, we will be deprecating all versions of SP1 before 3.0.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`sp1-recursion-circuit`	all versions	3.0.0`cargo update -p sp1-recursion-circuit --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 sp1-recursion-circuit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sp1-recursion-circuit to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8m24-3cfx-9fjw 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

During proof generation, the prover must observe all values sent to the verifier to generate valid Fiat-Shamir challenges. Prior to v3.0.0 the cumulative sum of the permutation argument was not observed when sampling zeta, which is a random challenge sampled to force the constraints to be true. In v3.0.0, this is fixed by observing the cumulative sum into the challenger, which can is done by observing the commit to the entire permutation trace. While this vulnerability is theoretically present in v2.0.0 and below, exploiting it is quite a difficult task as the cumulative sum one can get from

O3 Security · Impact-Aware SCA

Is GHSA-8m24-3cfx-9fjw in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works