GHSA-m95p-425x-x889 — cggmp21
Fix: LFDT-Lockness/cggmp21@60e0adaGHSA-m95p-425x-x889 is a CWE-345 vulnerability in cggmp21. A fix is available for cggmp21 — see the affected versions and patch details below.
cggmp21 has a missing check in the ZK proof used in CGGMP21
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-m95p-425x-x889.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
cggmp21🦀cggmp24Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Impact
cggmp21 concerns a missing check in the ZK proof that enables an attack in which a single malicious signer can reconstruct full private key.
Patches
cggmp21 v0.6.3is a patch release that contains a fix that introduces this specific missing check- However, cggmp21 recommends upgrading to
cggmp24 v0.7.0-alpha.2which contains many other security checks as a precaution. Follow migration guideline to upgrade.
Workarounds
Update to cggmp21 v0.6.3, a minor release that contains a minimal security patch.
However, for full mitigation, users will need to upgrade to cggmp24 v0.7.0-alpha.2 as it contains many more security check implementations.
Resources
Read this blog post to learn more.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | cggmp21 | all versions | 0.6.3cargo update -p cggmp21 --precise 0.6.3 |
| 🦀crates.io | cggmp24 | all versions | 0.7.0-alpha.2cargo update -p cggmp24 --precise 0.7.0-alpha.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cggmp21, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cggmp21 to 0.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m95p-425x-x889 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m95p-425x-x889 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-m95p-425x-x889. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-m95p-425x-x889 in your dependencies?
O3 Security finds GHSA-m95p-425x-x889 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.