Succinct patches SP1 zero-knowledge proving bug that exposed Prover Network

Succinct patched a high-severity soundness bug in its SP1 zero-knowledge proving system that exposed its mainnet Prover Network to invalid execution proofs. The vulnerability affected native Rust verifiers in sp1_hypercube, sp1_prover, and sp1_sdk versions 6.0.0 through 6.8.0 due to a failure to validate Tensor dimension lengths. Discovered by Vitalis Salis via Immunefi, Succinct released version 6.8.1 on September 24, 2026, fixing the flaw before publishing an advisory on October 11, 2026.

Patch release and remediation

• ▪Succinct advised users running native Rust verifiers in SP1 who accept proofs from untrusted provers to upgrade their software to version 6.8.1
• ▪Succinct released version 6.8.1, which patched a high-severity soundness bug in SP1, on September 24, 2026, 17 days before publishing GitHub security advisory GHSA-p7v2-jjv3-8p8f on October 11, 2026
• ▪Succinct deployed the version 6.8.1 patch for SP1's soundness bug to the mainnet Prover Network, requiring no configuration changes from users requesting network proofs

Technical details of the vulnerability

• ▪SP1 stores multidimensional data in Tensors, where SP1's native Rust verifier failed to check whether the number of stored elements matched the product of the tensor's declared dimensions
• ▪An attacker could exploit SP1 by supplying proof data with mismatched size labels, causing the native Rust verifier to accept an invalid proof

Scope of affected SP1 deployments

• ▪A high-severity soundness bug in Succinct's SP1 zero-knowledge proving system exposed Succinct's mainnet Prover Network to invalid execution proofs from third-party provers
• ▪Succinct stated in GitHub security advisory GHSA-p7v2-jjv3-8p8f that its mainnet Prover Network was the only known deployment affected by a high-severity soundness bug in SP1's proving system
• ▪The SP1 soundness flaw affected native Rust verification in sp1_hypercube, sp1_prover, and sp1_sdk versions 6.0.0 through 6.8.0

Unaffected proof checks and verifiers

• ▪On-chain Solidity verifiers for Groth16 and Plonk checks and applications whose proof aggregation ended in Groth16 or Plonk proofs were unaffected by SP1's high-severity soundness bug
• ▪Groth16 and Plonk proof checks in SP1 remained safe because they used wrapped proofs with fixed shapes that bypassed prover-controlled tensor formats