CVE-2025-58157: Consensys gnark · Uncontrolled Resource Consumption
Affects Consensys gnarkSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 0.13.0 : patch Consensys gnark soon.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.13.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Consensys gnark | Affected
| Fixed in– |
AI-suggested
European organizations should urgently upgrade gnark to version 0.13.0 or later, where the vulnerability has been patched. In addition, they should implement input validation and rate limiting on scalar multiplication requests to prevent abuse with malicious inputs that trigger the fake-GLV algorithm's slow convergence. Monitoring resource usage patterns and setting thresholds for CPU and memory consumption can help detect and mitigate ongoing attacks. Deploying gnark within containerized or sandboxed environments with resource quotas can limit the impact of potential DoS attempts. Organizations should also review their cryptographic workflows to identify any dependencies on vulnerable gnark versions and coordinate with vendors or internal teams to ensure timely patching. Finally, maintaining an incident response plan that includes DoS scenarios related to cryptographic components will improve resilience.
Description
gnark is a zero-knowledge proof system framework. In version 0.12.0, there is a potential denial of service vulnerability when computing scalar multiplication is using the fake-GLV algorithm. This is because the algorithm didn't converge quickly enough for some of the inputs. This issue has been patched in version 0.13.0.
References
- github.com/Consensys/gnark/security/advisories/GHSA-9fvj-xqr2-xwg8 (opens in a new tab)
- github.com/Consensys/gnark/issues/1483 (opens in a new tab)
- github.com/Consensys/gnark-crypto/commit/56600883e0e9f9b159e9c7000b94e76185ec3d0d (opens in a new tab)
- github.com/Consensys/gnark/commit/68be6cede36e387ab760725beabd3c96cc94e6dc (opens in a new tab)