CVE-2025-66017: cggmp24 and cggmp21 are vulnerable to signature forgery through altered presignatures
Affects cggmp21Source GCVE Database
Not known to be exploited · CVSS 8.2 High : upgrade to 0.7.0-alpha.2 soon.
Data as of 19 Nov 2026, 02:13 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 8.2 |
|---|
- Patch
- Available – fixed in 0.7.0-alpha.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 18 Nov 2026.
What to do
Upgrade cggmp24 to 0.7.0-alpha.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| crates.iocggmp21 | Affected
| Fixed in– |
| crates.iocggmp24 | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
### Impact This attack is against presignatures used in very specific context: * Presignatures + HD wallets derivation: security level reduces to 85 bits \ Previously users could generate a presignature, and then choose a HD derivation path while issuing a partial signature via [`Presignature::set_derivation_path`](https://docs.rs/cggmp21/0.6.3/cggmp21/signing/struct.Presignature.html#method.set_derivation_path), which is malleable to attack that reduces target security level. To mitigate, this method has been removed from API. * Presignatures + "raw signing" (when signer signs a hash without knowing an original message): results into signature forgery attack \ Previously, users were able to configure [`Presignature::issue_partial_signature`](https://docs.rs/cggmp21/0.6.3/cggmp21/signing/struct.Presignature.html#method.issue_partial_signature) with hashed message without ever providing original mesage. In new API, this method only accepts digests for which original message has been observed. ### Patches `cggmp24 v0.7.0-alpha.2` release contains API changes that make it impossible to use presignatures in contexts in which it reduces security. Follow [migration guidelines](https://github.com/LFDT-Lockness/cggmp21/blob/v0.7.0-alpha.2/CGGMP21_MIGRATION.md) to upgrade. ### Workarounds Users can continue using un-patched versions of library as long as they don't use presignatures in said scenarios where it weakens system security. To be sure, migrate to patched version that excludes presignatures from being used in such scenarios. ### References Read this [blog post](https://www.dfns.co/article/cggmp21-vulnerabilities-patched-and-explained) to learn more.
References
- github.com/LFDT-Lockness/cggmp21/security/advisories/GHSA-8frv-q972-9rq5 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2025-66017 (opens in a new tab)
- github.com/LFDT-Lockness/cggmp21/commit/9d98157e151596573cb071da59d27a4e0ac9b8dc (opens in a new tab)
- github.com/LFDT-Lockness/cggmp21 (opens in a new tab)
- rustsec.org/advisories/RUSTSEC-2025-0127.html (opens in a new tab)
- rustsec.org/advisories/RUSTSEC-2025-0128.html (opens in a new tab)
- dfns.co/article/cggmp21-vulnerabilities-patched-and-explained (opens in a new tab)