A critical security flaw in GPGME – the widely used library that enables applications to work with GnuPG – can allow attackers to leak sensitive app data through crafted OpenPGP keys. Identified as CVE-2026-129975, the vulnerability impacts all versions of GPGME prior to 2.3.1, whether invoked as a shared library, DLL, or bundled statically into programs. It affects email clients, XMPP tools, Samba, Gpg4win, and desktop packages mixing GnuPG with GUI layers.
How the Bug Works
The flaw arises when an OpenPGP key with an unusually long user ID triggers a double-free memory error. Two routines — read_status() and read_colon_line() — handle status lines and key listings from GnuPG. If such routines need to move data into a larger buffer due to length but incur an error part way, they may leave behind a pointer to already freed memory. A cleanup process then frees that memory again, leading to potential memory corruption. Such bugs often enable attackers to read or manipulate memory, possibly exposing private data or even leading to remote code execution.
Scope & Exposure
Software that relies on GPGME before version 2.3.0 is vulnerable. This includes many mail and chat clients, file-sharing services like Samba, and desktop suites such as Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop. Even applications that statically include older copies of GPGME are exposed, because updating the shared system library won’t fix embedded versions.
So far, no active exploitation of the flaw has been reported. However, GnuPG’s team warns that remote code execution cannot be ruled out given the nature of memory corruption. The bug was discovered by researcher Johan Carlsson and reported by GitLab just last week. It was supposed to be disclosed on November 25, but the disclosure date was moved up due to pressure from a different high-severity issue. Fixed versions have been released to address the risk.
What to Do Now
The patched version is GPGME 2.3.1. Users of shared or DLL‐based installations should update to 2.3.1 from official sources. Windows users should install Gpg4win 5.1.2, which bundles the fixed library. For installations on the legacy branch, version 1.24.4 includes the fix. Applications that statically include GPGME must be rebuilt to integrate the new library. There is no workaround available for those unable to update immediately.
Why this matters: GPGME is foundational for many encryption-aware apps. Vulnerabilities here ripple outward: encrypted email software, chat tools, file servers – all could leak data or be coerced into executing malicious code if they use vulnerable versions. Patching is essential.
As organizations rush to update, watch for downstream tools or dependencies that bundle older GPGME versions. Even a secure system can become at risk if one component is left behind. This incident underscores the importance of maintaining up-to-date cryptographic libraries — any lapse can lead to outsized exposure. Keeping encryption tools secure is only part of the job; ensuring every piece of the chain is trustworthy is just as critical.