Duplicate Advisory: Consensys gnark-crypto allows Signature MalleabilityGHSA-9xfq-8j3r-xp5g
CRITICALFix: Consensys/gnark-crypto#449GHSA-9xfq-8j3r-xp5g is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in github.com/Consensys/gnark-crypto. A fix is available for github.com/Consensys/gnark-crypto — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-9xfq-8j3r-xp5g.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/Consensys/gnark-crypto🐹github.com/consensys/gnark-cryptoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-fr8m-434r-g3xp. This link is maintained to preserve external references.
Original Description
Consensys gnark-crypto through 0.11.2 allows Signature Malleability. This occurs because deserialisation of EdDSA and ECDSA signatures does not ensure that the data is in a certain interval.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/Consensys/gnark-crypto | all versions | 0.12.0go get github.com/Consensys/gnark-crypto@v0.12.0 |
| 🐹Go | github.com/consensys/gnark-crypto | all versions | 0.12.0go get github.com/consensys/gnark-crypto@v0.12.0 |
Affected Products
gnark-cryptoconsensysDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/Consensys/gnark-crypto, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/Consensys/gnark-crypto to 0.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9xfq-8j3r-xp5g is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is GHSA-9xfq-8j3r-xp5g in your dependencies?
Find it across Go, including transitive dependencies.