GHSA-8m24-3cfx-9fjw — sp1-recursion-circuit
Fix: succinctlabs/sp1@79884ffGHSA-8m24-3cfx-9fjw is a security vulnerability in sp1-recursion-circuit. A fix is available for sp1-recursion-circuit — see the affected versions and patch details below.
sp1 has insufficient observation of cumulative sum
Real-World Exposure
sp1-recursion-circuitReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | sp1-recursion-circuit | all versions | 3.0.0cargo update -p sp1-recursion-circuit --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 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8m24-3cfx-9fjw can be triaged on real exposure rather than presence alone.
Tailored to GHSA-8m24-3cfx-9fjw. 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-8m24-3cfx-9fjw in your dependencies?
O3 Security finds GHSA-8m24-3cfx-9fjw across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.