CVE-2025-66017: Cggmp21 Cggmp24 And Cggmp21 Are Vulnerable Vulnerability
HIGHCVE-2025-66017 is a HIGH cggmp24 and cggmp21 are vulnerable vulnerability (CWE-327: Use of a Broken or Risky Cryptographic Algorithm) affecting Cggmp21 libraries in the crates.io ecosystem. The issue involves cggmp24 and cggmp21 are vulnerable to signature forgery through altered presignatures. Remediation is available by upgrading affected packages to version 0.7.0-alpha.2.
CVE-2025-66017 at a Glance
How to Fix CVE-2025-66017
To remediate this vulnerability, upgrade all affected Cggmp21 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade cggmp21 to Latest secure release
Upgrade cggmp24 to 0.7.0-alpha.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for cggmp21
How to Check if You Are Affected
To determine whether your application is affected by CVE-2025-66017, inspect your project dependencies for Cggmp21:
inspect dependencies for cggmp21
Analyze the terminal output to locate any version of Cggmp21 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.7.0-alpha.2), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm, where the product uses a broken or risky cryptographic algorithm or protocol. In Cggmp21, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-66017 Affected Cggmp21 Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
cggmp21
|
crates.io |
≤ 0.6.3
|
|
|
cggmp24
|
crates.io |
< 0.7.0-alpha.2
|
0.7.0-alpha.2
|
References
Frequently Asked Questions
What is CVE-2025-66017?
Which Cggmp21 versions are affected?
What version fixes CVE-2025-66017?
Is cggmp21 affected?
Is cggmp24 affected?
What CWE is associated with CVE-2025-66017?
How can I check crates.io dependencies for CVE-2025-66017?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-8frv-q972-9rq5",
"modified" : "2025-11-27T09:00:00Z",
"published" : "2025-11-25T20:42:28Z",
"aliases" : [ "CVE-2025-66017" ],
"summary" : "cggmp24 and cggmp21 are vulnerable to signature forgery through altered presignatures",
"details" : "### Impact\nThis attack is against presignatures used in very specific context:\n* Presignatures + HD wallets derivation: security level reduces to 85 bits \\\n 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.\n* Presignatures + \"raw signing\" (when signer signs a hash without knowing an original message): results into signature forgery attack \\\n 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.\n\n### Patches\n`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.\n\n### Workarounds\nUsers 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.\n\n### References\nRead this [blog post](https://www.dfns.co/article/cggmp21-vulnerabilities-patched-and-explained) to learn more.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "crates.io",
"name" : "cggmp21"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "0.6.3"
} ]
} ]
}, {
"package" : {
"ecosystem" : "crates.io",
"name" : "cggmp24"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.7.0-alpha.2"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/LFDT-Lockness/cggmp21/security/advisories/GHSA-8frv-q972-9rq5"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-66017"
}, {
"type" : "WEB",
"url" : "https://github.com/LFDT-Lockness/cggmp21/commit/9d98157e151596573cb071da59d27a4e0ac9b8dc"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/LFDT-Lockness/cggmp21"
}, {
"type" : "WEB",
"url" : "https://rustsec.org/advisories/RUSTSEC-2025-0127.html"
}, {
"type" : "WEB",
"url" : "https://rustsec.org/advisories/RUSTSEC-2025-0128.html"
}, {
"type" : "WEB",
"url" : "https://www.dfns.co/article/cggmp21-vulnerabilities-patched-and-explained"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-327" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2025-11-25T20:42:28Z",
"nvd_published_at" : "2025-11-25T20:16:00Z"
}
}