What is GHSA-F77Q-R5QM-W4M8?

GHSA-F77Q-R5QM-W4M8 is a medium-severity security vulnerability in sp1-recursion-gnark-ffi (rust), affecting versions < 1.2.0. It is fixed in 1.2.0.

How severe is GHSA-F77Q-R5QM-W4M8?

GHSA-F77Q-R5QM-W4M8 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of sp1-recursion-gnark-ffi are affected by GHSA-F77Q-R5QM-W4M8?

sp1-recursion-gnark-ffi (rust) versions < 1.2.0 is affected.

Is there a fix for GHSA-F77Q-R5QM-W4M8?

Yes. GHSA-F77Q-R5QM-W4M8 is fixed in 1.2.0. Upgrade to this version or later.

Is GHSA-F77Q-R5QM-W4M8 exploitable, and should I be worried?

Whether GHSA-F77Q-R5QM-W4M8 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-F77Q-R5QM-W4M8 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-F77Q-R5QM-W4M8 in sp1-recursion-gnark-ffi

Q: How severe is GHSA-F77Q-R5QM-W4M8?

GHSA-F77Q-R5QM-W4M8 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of sp1-recursion-gnark-ffi are affected by GHSA-F77Q-R5QM-W4M8?

sp1-recursion-gnark-ffi (rust) versions < 1.2.0 is affected.

Q: Is there a fix for GHSA-F77Q-R5QM-W4M8?

Yes. GHSA-F77Q-R5QM-W4M8 is fixed in 1.2.0. Upgrade to this version or later.

Q: Is GHSA-F77Q-R5QM-W4M8 exploitable, and should I be worried?

Whether GHSA-F77Q-R5QM-W4M8 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-F77Q-R5QM-W4M8 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-F77Q-R5QM-W4M8?

Upgrade sp1-recursion-gnark-ffi to 1.2.0 or later.

Summary

sp1-recursion-gnark-ffi has insufficient range checks of BabyBear arithmetic

The Gnark recursion circuit constrains arithmetic over BabyBear when the native field of the ZKP circuit is the BN254 scalar field. Proper implementation of this logic requires range checking Bn254 values to be less than the BabyBear modulus.

In versions < 1.2.0, functions like InvF and InvE used values generated by hints that were not appropriately range checked. These issues are resolved in versions 1.2.0 and higher, by adding range checks in the appropriate places. This code was covered under the original audit scope of the recursion circuit audit by Veridise, and both Veridise and Kalos revisited the code for similar issues and found no additional vulnerabilities.

This issue was discovered by the Succinct team on September 3rd. The issue was fixed and resolved within 48 hours, and released with V1.2.0 (note that a later V2.0.0 release has the same contents as V1.2.0 to respect semver), with production SP1 users being notified and upgraded immediately. The V1.1.0 verifier was frozen on September 4th to ensure that no one uses versions of SP1 with this bug.

Impact

GHSA-F77Q-R5QM-W4M8 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.2.0); upgrading removes the vulnerable code path.

Affected versions

sp1-recursion-gnark-ffi (< 1.2.0)

Security releases

sp1-recursion-gnark-ffi → 1.2.0 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade sp1-recursion-gnark-ffi to 1.2.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-F77Q-R5QM-W4M8? GHSA-F77Q-R5QM-W4M8 is a medium-severity security vulnerability in sp1-recursion-gnark-ffi (rust), affecting versions < 1.2.0. It is fixed in 1.2.0.
How severe is GHSA-F77Q-R5QM-W4M8? GHSA-F77Q-R5QM-W4M8 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of sp1-recursion-gnark-ffi are affected by GHSA-F77Q-R5QM-W4M8? sp1-recursion-gnark-ffi (rust) versions < 1.2.0 is affected.
Is there a fix for GHSA-F77Q-R5QM-W4M8? Yes. GHSA-F77Q-R5QM-W4M8 is fixed in 1.2.0. Upgrade to this version or later.
Is GHSA-F77Q-R5QM-W4M8 exploitable, and should I be worried? Whether GHSA-F77Q-R5QM-W4M8 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-F77Q-R5QM-W4M8 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-F77Q-R5QM-W4M8? Upgrade sp1-recursion-gnark-ffi to 1.2.0 or later.