A critical vulnerability has been identified in GPGME, the library commonly used by applications to integrate with GnuPG, due to a malicious OpenPGP key with an unusually long user ID. This flaw, which could potentially allow attackers to access sensitive application data, has prompted the GnuPG project to release updated versions to address the issue.
Details of the GPGME Vulnerability
The vulnerability, identified as CVE-2026-129975, affects all versions of GPGME prior to 2.3.0, regardless of how the library is integrated into the software—be it as a shared library, a Windows DLL, or through static linking. This issue affects a wide range of applications, including most email clients, many XMPP clients, and various GnuPG packages such as Gpg4win and GnuPG Desktop.
The problem arises from a double free error in the library’s functions that process status lines and key listings. When handling excessively long input, these functions may attempt to manage memory inadequately, leading to potential data exposure. While no known exploits have been reported, the possibility of remote code execution cannot be discounted.
Identifying and Addressing the Flaw
Johan Carlsson discovered the vulnerability, which was subsequently reported to the GnuPG project by GitLab. Originally slated for disclosure on November 25, the announcement was expedited due to the emergence of another security issue, Ruby2Shell, necessitating an earlier response.
The updated version, GPGME 2.3.1, resolves the flaw and is now available. Notably, GPGME 2.3.0 was never released to the public. The update process varies depending on the implementation: for shared libraries or DLLs, updating to GPGME 2.3.1 is essential. Windows users should update to Gpg4win 5.1.2, which includes the fixed library. For legacy systems unable to upgrade, a patch is available, and a separate release, version 1.24.4, addresses the issue for older branches.
Recommendations and Future Outlook
Users are urged to update their software immediately to avoid potential security breaches. Applications containing bundled or statically linked versions of the library must be rebuilt with the updated release to ensure security. Notably, GPGMEPP and GPGMEQT are not impacted and do not require updates.
The GnuPG project has not provided any interim solutions for systems unable to update. Thus, applying the latest patches is crucial to maintaining data security. Staying informed about such vulnerabilities and responding promptly to updates is essential in today’s rapidly evolving digital landscape.
