A critical security vulnerability in GPGME, the library used by applications to interact with GnuPG, could allow attackers to expose data from affected software through specially crafted OpenPGP keys. The flaw, tracked as CVE-2026-129975, involves a memory-management error that can be triggered by a key containing an unusually long user ID. The GnuPG project disclosed the issue on 20 November 2026 and released GPGME version 2.3.1 to address it. According to the project’s security advisory, the vulnerability could be used to extract information from applications by sending them signed data containing a maliciously crafted key. The project also stated that remote code execution cannot be ruled out, although this possibility should not be interpreted as confirmation that attackers have successfully achieved code execution through the flaw. The issue was discovered by security researcher Johan Carlsson, with GitLab informing the GnuPG project on 12 November. The disclosure was initially scheduled for 25 November but was brought forward to 20 November following an earlier update to the disclosure schedule associated with the Ruby2Shell vulnerability. The project’s advisory identifies the issue internally as T8557 and recommends that users update affected installations as soon as possible.
The vulnerability is caused by a double-free error, a memory-management problem that occurs when software attempts to release the same memory allocation more than once. The affected code is located in two internal GPGME routines, read_status() and read_colon_line(), which process status information and key listings returned by GnuPG. The project’s technical explanation states that these routines initially allocate a buffer of 1,024 bytes and expand it when incoming information requires additional space. During this process, the routines can use a newly allocated memory address without immediately updating the corresponding pointer stored in the application context. If an error or another unexpected event causes a routine to exit before that update is completed, the context can retain a pointer to memory that has already been released. When the context is subsequently cleaned up, the software may attempt to free that memory again, resulting in the double-free condition. The technical details are documented in the project’s official tracker entry. The potential impact includes data exposure in applications that process affected input through the vulnerable library. The advisory gives signed data as an example of how the issue could be triggered, but it does not establish that every application using GPGME automatically processes such material without additional user or application interaction.
According to the GnuPG project, the vulnerability affects software using GPGME versions before 2.3.0, whether the library is installed as a shared library, provided as a Windows DLL or statically linked into an application. The advisory notes that version 2.3.0 was never publicly released. Applications identified as examples of software using GPGME include most mail clients, many XMPP clients, Samba, Gpg4win, GnuPG Desktop and GnuPG VS-Desktop. This means that exposure is not limited to users who have installed GPGME separately, as applications may include their own bundled copies of the library. Updating a system-wide shared library will not automatically fix software that contains a statically linked or separately bundled version. Developers and administrators therefore need to check the GPGME version used by individual applications and obtain rebuilt releases where necessary. The project has released GPGME 2.3.1 as the corrected version and made it available through its official download page. The security advisory provides further technical information, affected configurations and instructions for obtaining the update. For Windows users, Gpg4win 5.1.2 includes the corrected GPGME library. Its official release notes identify the update as a security fix for CVE-2026-129975 and recommend installing it as soon as possible.
For systems that cannot immediately move to GPGME 2.3.1, the project has also provided a patch intended to address the underlying memory-management issue in older versions. Administrators maintaining older software should assess whether the patch can be applied safely or whether an updated application build is available from its developer. The GnuPG advisory specifically highlights the need to rebuild statically linked applications against the corrected library, since replacing a shared system component will not update code already included in an application binary. Users should also check whether their software vendors have issued updated packages containing the security fix rather than assuming that installing the latest standalone library is sufficient. The advisory states that GPGMEPP and GPGMEQT do not require updates for this issue. The project has not provided an interim workaround for applications that cannot yet be updated, making the availability of a corrected release or an applicable patch particularly important for affected deployments. Further information, including the source release and update guidance, is available through the GnuPG project and its published security announcement. Organisations using email clients, file-sharing software or other applications that depend on GPGME should identify bundled library versions and coordinate updates with their software providers to reduce the risk associated with the vulnerability.
Follow the SPIN IDG WhatsApp Channel for updates across the Smart Pakistan Insights Network covering all of Pakistan’s technology ecosystem.





