External risk intelligence

CGGMP24 ECDSA TSS Missing ZK Proof Check Allows Private Key Reconstruction

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2025-66016

CGGMP24 is a cryptographic library used for multiparty computation and signing protocols. It is a developer-focused toolkit integrated into applications rather than a standalone network service, appliance, or edge gateway. Consequently, it lacks direct public internet exposure in common deployment patterns.

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability exists in a cryptographic protocol that could allow a single malicious participant to reconstruct a full private key. This issue impacts systems using the affected version of the protocol, potentially compromising sensitive cryptographic operations.

A flaw allows a single bad actor to steal private keys.
Protects sensitive cryptographic operations from theft.
Confirm relevance and assess exposure to this threat.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by interacting with a system that uses a vulnerable version of the CGGMP24 protocol. This interaction would leverage a flaw in the Zero-Knowledge proof mechanism, allowing a single malicious participant to gain access to the full private key. This compromised key could then be used for further malicious activities.

Requires an unprotected entry point.
Triggered by a flawed Zero-Knowledge proof.
Enables full private key reconstruction.

Live Threat

Current exploitation, exposure, and threat context

The CGGMP24 protocol's missing check in its ZK proof could allow a malicious signer to reconstruct the full private key. This could affect the integrity of cryptographic operations when supported by the advisory.

Private key reconstruction.
Malicious signer reconstructs key.
Compromised cryptographic operations.

Operational Fix

Recommended remediation, mitigation, and detection steps

The CGGMP24 cryptographic library's vulnerability, affecting versions prior to 0.6.3, requires careful ownership and triage. Platform or infrastructure teams are likely responsible for managing this library, as it's an integrated component rather than a standalone service. The initial practical move is to identify all deployments, confirm their criticality and reachability, and then coordinate remediation with the responsible teams, possibly including vendor engagement if the library is part of a third-party product.

Platform or infrastructure teams own this.
Verify all CGGMP24 deployments and criticality.
Plan upgrade or vendor coordination.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is the CGGMP24 library used for?

CGGMP24 is a specialized cryptographic toolkit designed for multi-party computation (MPC) and threshold signature schemes (TSS). Developers integrate it into applications to enable secure, distributed signing processes where multiple parties collaborate without any single participant initially holding the complete private key. It is a building block for privacy-focused digital asset management and authentication systems rather than an end-user application.

How does this vulnerability affect private keys?

This issue falls under CWE-345, which involves insufficient verification of data authenticity. In this context, a missing check in the protocol's Zero-Knowledge (ZK) proof allows a malicious participant to manipulate the signing process. By bypassing this verification step, an attacker can mathematically reconstruct the full private key from the data exchanged during the threshold signing protocol, effectively compromising the security of the entire system.

Does any interaction trigger this flaw?

Not every interaction triggers the bug. The vulnerability requires a malicious actor to participate directly as one of the signers in the threshold protocol. Because the flaw exists within the protocol's mathematical proof exchange, it cannot be triggered by simple external network probes or unrelated system traffic that does not actively participate in the cryptographic signing session.

Why is this CVE often deemed unlikely to be internet-facing?

According to Halo Surface Signal, CGGMP24 is a developer-focused library integrated into backend application logic rather than an independent service or appliance. Because it functions as a component embedded within private infrastructure to perform specific cryptographic tasks, it rarely possesses direct public internet exposure, making it difficult for unauthorized external actors to initiate a malicious signing session.

How should I address CVE-2025-66016 in my code?

First, conduct an inventory to identify which applications include CGGMP24 versions prior to 0.6.3. Once located, coordinate with your development or infrastructure teams to update the library. While version 0.6.3 contains the necessary fix for this specific proof issue, the advisory recommends upgrading to at least version 0.7.0-alpha.2, as it includes additional security hardening measures beyond the initial patch.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.