The GnuPG project has issued emergency patches to address a critical security vulnerability in GnuPG Made Easy (GPGME), the core programmatic interface used by numerous applications to integrate GnuPG functionality. The flaw allows an attacker to corrupt memory and potentially extract sensitive data or achieve arbitrary code execution by feeding malicious cryptographic material to target software.
The issue, designated as CVE-2026-129975, stems from improper memory handling when processing input containing an unusually long user ID. According to reporting by The Hacker News, while the project has not observed active exploitation in the wild, the severity of the flaw prompted an accelerated disclosure timeline.
Technical Mechanics of the Double-Free Flaw
The vulnerability is classified as a double-free memory error within two specific GPGME routines: read_status() and read_colon_line(). These functions handle parsing status messages and key listings received from underlying GnuPG processes.
When input lengths exceed standard boundaries, these routines dynamically allocate a larger memory buffer and reassign data pointers. However, the software only updates the pointer to the new memory address if the operation finishes without triggering an error. If a failure occurs midway, the routines leave a dangling pointer pointing to an allocation that has already been deallocated. Standard cleanup procedures then attempt to free that same memory block a second time.
This sequence allows an adversary to manipulate memory structures, leading to potential information disclosure from the host application. The project noted that remote code execution cannot be dismissed as an outcome of exploitation. An attack vector involves transmitting signed data containing a specially crafted OpenPGP key to an application that processes it through the library.
Widespread Software Exposure
CVE-2026-129975 affects all software built with GPGME versions prior to 2.3.0. Vulnerable implementations encompass shared libraries, Windows dynamically linked libraries (DLLs), and binaries that incorporate statically linked copies of the GPGME code.
The library is widely embedded across multiple ecosystems. Programs highlighted as vulnerable include:
- Most major desktop and server email clients leveraging GnuPG encryption.
- Various XMPP messaging clients.
- Samba network services.
- Official vendor suites, including GnuPG Desktop, GnuPG VS-Desktop, and Gpg4win packages.
GnuPG stated that high-level C++ and Qt wrapper components, specifically GPGMEPP and GPGMEQT, do not require direct fixes because the underlying core library houses the flawed logic.
Discovery and Coordinated Disclosure
Security researcher Johan Carlsson discovered the vulnerability, which was subsequently reported to the GnuPG team by GitLab. The original coordinated public disclosure was slated for November 25.
However, the disclosure date was moved forward after an unrelated vulnerability—the Ruby2Shell bug—forced GitLab to release an early update cycle, accelerating the need for public GnuPG advisories and fixes.
What Defenders and Administrators Should Do
The GnuPG team has confirmed there are no valid interim workarounds to mitigate the issue without upgrading. Security teams, software vendors, and system administrators must identify exposed software and apply available updates promptly.
- Upgrade Core Libraries: Administrators running dynamic installations should deploy GPGME version 2.3.1 immediately. Version 2.3.0 was skipped and never made publicly available.
- Address Legacy Deployments: Organizations operating older infrastructure unable to upgrade to the 2.x branch must apply the official standalone patch or move to GPGME 1.24.4. GnuPG maintainers noted they cannot guarantee future security fixes for the 1.x legacy branch indefinitely.
- Update Windows Suites: Windows deployments utilizing Gpg4win must upgrade to version 5.1.2, which bundles the corrected GPGME release. Gpg4win release notes classified the bug as severe and advised immediate installation.
- Recompile Statically Linked Applications: Software engineers who bundle or statically link GPGME within custom or third-party binaries must rebuild and redeploy their applications using GPGME 2.3.1, as OS-level shared library upgrades will not remediate static copies.





