Skip to content
Fencer Intel
high 7.5

CVE-2026-40323 json

SP1 V6 Recursion Circuit Row-Count Binding Gap

published 6mo ago modified 14d ago also GHSA-63x8-x938-vx33 , EUVD-2026-24062

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits
0
none known

Summary

SP1 is a zero‑knowledge virtual machine that proves the correct execution of programs compiled for the RISC-V architecture. In versions 6.0.0 through 6.0.2, a soundness vulnerability in the SP1 V6 recursive shard verifier allows a malicious prover to construct a recursive proof from a shard proof that the native verifier would reject. Version 6.1.0 fixes the issue.

Patch / fix

  • crates.io sp1_sdk 6.1.0
  • crates.io sp1_recursion_circuit 6.1.0
  • crates.io sp1_prover 6.1.0
  • succinct sp1 6.1.0

Is CVE-2026-40323 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
6mo ago

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 8.9 CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N
CNA 4.0 8.9 CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
crates.io sp1_sdk
>=6.0.0, <6.1.0
6.1.0
crates.io sp1_recursion_circuit
>=6.0.0, <6.1.0
6.1.0
crates.io sp1_prover
>=6.0.0, <6.1.0
6.1.0

Affected products

  • succinctlabs sp1

Classification

Weakness
  • CWE-345 Insufficient Verification of Data Authenticity
  • CWE-354 Improper Validation of Integrity Check Value

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.