CVE-2025-57801
📋 TL;DR
This vulnerability in gnark's signature verification allows signature malleability, enabling multiple distinct witnesses to satisfy the same public inputs. It primarily affects systems using gnark's EdDSA or ECDSA circuits for nullifiers or anti-replay checks, potentially allowing double spending attacks. Users of gnark versions before 0.14.0 are affected.
💻 Affected Systems
- gnark
📦 What is this software?
Gnark by Consensys
⚠️ Risk & Real-World Impact
Worst Case
Double spending attacks in cryptocurrency or payment systems, financial losses, and protocol integrity compromise.
Likely Case
Signature malleability enabling replay attacks or bypassing anti-replay mechanisms in affected applications.
If Mitigated
Limited impact if systems don't use signature-derived nullifiers or have additional validation layers.
🎯 Exploit Status
Exploitation requires understanding of zero-knowledge proofs and signature malleability techniques.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 0.14.0
Vendor Advisory: https://github.com/Consensys/gnark/security/advisories/GHSA-95v9-hv42-pwrj
Restart Required: No
Instructions:
1. Update gnark to version 0.14.0 or later. 2. Run 'go get github.com/consensys/gnark@v0.14.0'. 3. Rebuild and redeploy applications using gnark.
🔧 Temporary Workarounds
Manual signature validation
allAdd custom constraints to verify 0 ≤ S < order in signature verification circuits
Implement additional constraints in EdDSA/ECDSA circuit verification logic
🧯 If You Can't Patch
- Implement additional validation layers outside gnark circuits
- Monitor for duplicate nullifiers or replay attempts in application logic
🔍 How to Verify
Check if Vulnerable:
Check if using gnark version <0.14.0 and using EdDSA/ECDSA circuits with signature-derived nullifiersCheck Version:
go list -m github.com/consensys/gnarkVerify Fix Applied:
Verify gnark version is 0.14.0+ and test signature verification with malformed S values📡 Detection & Monitoring
Log Indicators:
- Multiple successful verifications with same public inputs
- Duplicate nullifier usage
Network Indicators:
- Repeated transactions with similar signatures
- Unusual verification patterns
SIEM Query:
Search for duplicate transaction IDs or nullifiers in application logs