VYPR
patchPublished Nov 21, 2026· 1 source

Critical GPGME Flaw Exposes Applications to Data Theft via Malicious OpenPGP Keys

GnuPG has released patches for a critical memory corruption vulnerability in its GPGME library, CVE-2026-129975, which could allow attackers to steal sensitive application data.

GnuPG has issued an urgent warning and released patches for a critical vulnerability affecting its widely-used GPGME library. The flaw, tracked as CVE-2026-129975, can be triggered by a specially crafted OpenPGP key containing an unusually long user ID, leading to a memory corruption bug. This vulnerability poses a significant risk to all applications that utilize GPGME versions prior to 2.3.0, potentially enabling attackers to exfiltrate sensitive data.

The GnuPG project has not yet reported any instances of this vulnerability being exploited in the wild. However, the advisory notes that remote code execution cannot be definitively ruled out. The attack vector involves signed data being passed to an application, which then forwards it to the GPGME library. While the exact circumstances under which programs pass such data without manual key import are not fully detailed, the potential for exploitation is clear.

At its core, the vulnerability is a double-free error, where the same block of memory is released twice. This occurs within two specific routines, read_status() and read_colon_line(), responsible for processing status lines and key listings returned by GnuPG. When processing excessively long input, these routines attempt to allocate a larger buffer. However, if an error occurs during this process, the library may incorrectly record the new memory address while leaving a dangling pointer to memory that has already been freed. Subsequent cleanup operations then attempt to free this already-released memory, leading to the critical memory corruption.

The flaw was discovered by Johan Carlsson and subsequently reported to the GnuPG project via GitLab. The planned public disclosure date was November 25, but it was accelerated due to an unrelated security issue that necessitated an earlier update from the project.

Fixed versions of the library have been released. The primary update is GPGME version 2.3.1, which addresses the vulnerability. For users on Windows, the Gpg4win 5.1.2 package includes the patched library and is recommended for immediate installation. For those unable to update to 2.3.1, a patch is available, and a fixed release for the legacy branch, 1.24.4, has also been provided, though the project notes that the legacy branch may not receive all security patches.

It is crucial to note that applications using GPGME either as a shared library, a Windows DLL, or statically linked are affected. This includes a wide range of software such as many email clients, XMPP clients, Samba, and GnuPG's own desktop packages. Applications with bundled or statically linked copies of the vulnerable library require their own rebuilt releases, as system-level updates to the shared library will not protect them.

While GPGMEPP and GPGMEQT do not require an update, the advisory offers no interim workaround for applications that cannot be immediately updated. Users and administrators are strongly advised to update affected applications and libraries as soon as possible to mitigate the risk of sensitive data exposure.

Synthesized by Vypr AI