GnuPG releases GPGME 2.3.1 to fix what it calls a critical double free (CVE-2026-129975) triggered by an OpenPGP key with a crafted very long user ID
The GnuPG project announced GPGME 2.3.1 on its info-gnu list on 20 November 2026 (19:01 UTC+1, 21 Nov 02:01 Perth (AWST)), saying it fixes a critical security bug found in all prior versions (source: GnuPG).
GnuPG says an OpenPGP key containing a crafted very long user ID can trigger a double free that can be used to exfiltrate data from applications, for example by sending signed data, and that remote code execution can't be ruled out, so an immediate update is highly suggested (source: GnuPG).
GnuPG says all software using a GPGME version prior to 2.3.0, as a shared library, DLL or statically linked, is affected, and gives Gpg4win, GnuPG Desktop, GnuPG VS-Desktop, most mail clients, many XMPP clients, Samba and Flatpak as examples of software using GPGME (source: GnuPG).
GnuPG says the bug was discovered by Johan Carlsson, was reported to it on 12 November 2026, and was disclosed on 20 November instead of the planned 25 November (source: GnuPG). GnuPG has also released Gpg4win 5.1.2 with the fixed GPGME, and offers a patch for older GPGME versions that cannot be updated (source: GnuPG).
The advisory does not say the flaw is being exploited.
- Product
- GPGME (GnuPG Made Easy) library, including Gpg4win, GnuPG Desktop and GnuPG VS-Desktop
- Versions
- Affected: all GPGME versions prior to 2.3.0 (2.3.0 was never publicly available). Fixed: GPGME 2.3.1; Gpg4win 5.1.2 includes the fixed GPGME. Per GnuPG, as of 21 Nov.
- CVSS
- Not given in the GnuPG advisory (GnuPG calls it a critical security bug)
- Exploited in Australia?
- unknown
- Patch to
- Update the GPGME shared library to 2.3.1 (rebuild statically linked binaries against 2.3.1); on Windows install Gpg4win 5.1.2; GnuPG offers a patch for older versions that cannot be updated (per GnuPG). No need to update GPGMEPP or GPGMEQT, per GnuPG.
