Private-key extraction via incomplete ZK-proof verification
Published Nov 25, 2025 · Updated Nov 25, 2025
Cryptographic verification failure in Lockness cggmp21 before 0.6.3 allows attackers controlling one signer to reconstruct the private key. The Paillier-Blum modulus ZK-proof verifier used during auxiliary key generation accepts a proof without performing a required integrity check. Control of one protocol signer is sufficient, breaking the threshold guarantee and exposing the complete ECDSA signing key.
Summary
What happened
Cryptographic verification failure in Lockness cggmp21 before 0.6.3 allows attackers controlling one signer to reconstruct the private key. The Paillier-Blum modulus ZK-proof verifier used during auxiliary key generation accepts a proof without performing a required integrity check. Control of one protocol signer is sufficient, breaking the threshold guarantee and exposing the complete ECDSA signing key.
The record
- CVE
- CVE-2025-66016
- Published
- Nov 25, 2025
- Updated
- Nov 25, 2025
- Vendor
- Lockness
- Product
- cggmp21
- Classifications
- CWE-347, CWE-345, T1552.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 25, 2025CVE publishedPublication date reported by the CVE source.
- Nov 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.6.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo