The Ledger
Succinct Discloses SP1 Rust Verifier Bug Affecting V6
Succinct disclosed a high-severity soundness flaw in SP1 V6’s native Rust verifier, affecting versions 6.0.0 through 6.8.0. The flaw could let malformed Core or Compressed proofs pass; Succinct says its Prover Network now uses the patch in version 6.8.1.

“A soundness vulnerability in SP1 V6 allows a malicious prover to supply proof tensors whose declared dimensions disagree with their storage length.”
SP1 security advisory
Succinct disclosed the high-severity flaw on October 11, 2026, in an advisory for its SP1 zero-knowledge virtual machine. The bug affects the native Rust verifier in versions 6.0.0 through 6.8.0 and could cause it to accept a proof for an invalid execution. Succinct says the issue is fixed in version 6.8.1 and that its mainnet Prover Network has been updated.
A malformed tensor could break verification
SP1’s verifier represents multidimensional proof data as tensors: each has a storage buffer and declared dimensions describing its shape. The number of stored elements should equal the product of those dimensions, but the affected code did not check that relationship during deserialization. Later verification paths used the declared dimensions without checking the underlying storage.
A malicious prover could supply a tensor whose declared shape and storage length did not match. Different verification stages could then process different portions of the same data, breaking the consistency needed for sound verification. The advisory says the flaw applies to Core and Compressed proofs submitted directly to the affected native Rust verifier, exposing applications that accept such proofs from untrusted provers.
On-chain Groth16 and Plonk checks are outside the flaw
The advisory says Groth16 and Plonk verification are unaffected because those paths use wrapped proofs with fixed shapes, rather than the proof-controlled Rust tensor representation involved in the bug. Compressed proofs checked through the verify_sp1_proof library function are unaffected only when aggregation ends with a Groth16 or Plonk proof.
Exploitation requires an attacker to submit proofs to an affected native Rust verifier. Succinct identifies its own mainnet Prover Network—which accepted proofs from third-party provers—as the only known affected deployment at the time of the finding. The advisory says requester exposure depended on the proof mode and verification path; it does not provide a count of potentially exposed requests.
Version 6.8.1 adds length and shape checks
The patch rejects tensors during deserialization when their storage length differs from the product of their declared dimensions. It also checks physical tensor shapes in affected verifier paths before processing stored elements. Succinct says it deployed the fix to the Prover Network after version 6.8.1 became available and that requesters using that network do not need to change their integration.
SP1’s release page dates version 6.8.1 to September 24, 2026—17 days before the advisory was published. The fix applies to sp1_hypercube, sp1_prover and sp1_sdk; the advisory lists versions 6.0.0 through 6.8.0 as affected and 6.8.1 as patched. Teams operating their own native Rust verifier for proofs from untrusted provers are told to upgrade to 6.8.1.
Vitalis Salis receives credit for the finding
Succinct credits Vitalis Salis with identifying the vulnerability through the Immunefi bug bounty program. The advisory lists the severity as high and says no CVE is known. Its scope is specific: the risk described concerns native Rust verification of certain proof types, not the on-chain Groth16 and Plonk verification paths.
For teams assessing exposure, the distinction is whether their application directly runs an affected native Rust verifier on proofs supplied by untrusted parties. Succinct’s stated remediation is version 6.8.1; its advisory separately confirms the Prover Network has been updated.
Sources
- Original source GitHub — Succinct Labs · page 1 github.com
Other pages read
- GitHub — Succinct Labs · page 2 github.com
Related stories
- Researchers Cut a Depth-32 Privacy Proof to 28.6 Milliseconds
- GRIDSHIELD Preprint Proposes Order-Independent Clearing for P2P Energy Trading
- Preprint presents BioBind protocol for biometric zero-knowledge authentication
- Paper Finds ZK Rewards Raised Attackers’ Share in Federated Learning Tests
- Researchers test Besu system for private local energy settlement