GnuPG announces GPGME 2.3.1 to patch CVE-2026-129975 double-free flaw
GnuPG released GPGME 2.3.1 to fix CVE-2026-129975, a double-free in status-line and key-listing parsing that can leak data and may enable remote code execution. The flaw affects all GPGME versions before 2.3.0 and therefore many applications that rely on GnuPG for encryption and signing. Maintainers recommend immediate library updates, patched Gpg4win packages, or applying the supplied patch to older builds.
GnuPG maintainer Werner Koch announced GPGME 2.3.1 on Nov. 20, 2026, and dated the release Nov. 19. The update fixes CVE-2026-129975, a critical double-free bug in code that reads status lines and key listings from gpg. A crafted OpenPGP key with a very long user ID can trigger the flaw. Koch said the bug can exfiltrate data from applications by sending signed data and that remote code execution cannot be ruled out, making immediate updates highly recommended.
The advisory gives a root cause: GPGME functions that parse status lines and key listings start with a 1,024-byte buffer and reallocate it when needed. The new pointer is used inside the function, but the context object is updated only at the end. If an early return follows a read error, the context keeps a stale pointer to freed memory. When the context is later released, that memory can be freed again. Other allocations may prevent allocator double-free checks from firing. GitLab reported the issue on Nov. 12, and disclosure was accelerated from Nov. 25 due to Ruby2Shell.
The impact is broad because GPGME is the library many applications use to call GnuPG for encryption, signing, and key handling. The advisory says all software using GPGME before 2.3.0 is affected, whether linked dynamically or statically. Named examples include Gpg4win, GnuPG Desktop, GnuPG VS-Desktop, most mail clients, many XMPP clients, Samba, and Flatpak. Version 2.3.0 was never publicly available, so users of earlier releases need the fix. The maintainers also say a patch can be applied to older GPGME versions, while GPGMEPP and GPGMEQT do not require updates.
The stakes are high because the bug sits below applications, not in one product. Mail clients, chat tools, Windows suites, file services, and desktop signing tools can inherit the same parser flaw through GPGME. A crafted key can trigger the flaw, while signed data can be used for exfiltration. RCE is not confirmed, but the advisory treats it as a realistic possibility. The practical consequence is that updating the shared library, or rebuilding statically linked binaries against GPGME 2.3.1, is the only documented mitigation.
Users and operators of GPGME-dependent applications, including mail clients, XMPP clients, Samba, Flatpak, Gpg4win, and GnuPG desktop tools, need to update the shared library or rebuild static binaries against GPGME 2.3.1 to remove a data-leak and possible remote-code-execution path.
Sources (1)
- [1]RCE in Gnupg(https://lists.gnupg.org/pipermail/gnupg-announce/2026q4/000517.html)