GnuPG announced GPGME 2.3.1 on November 20 to fix CVE-2026-129975, a double free that the project calls a critical security bug present in all earlier versions. GPGME is the library that programs use to work with GnuPG.
According to the GnuPG security advisory, an OpenPGP key with a crafted, very long user ID can trigger the double free, and the flaw can be used to exfiltrate data from applications, for example by sending signed data. GnuPG says remote code execution cannot be ruled out and recommends an immediate update. The advisory does not report any exploitation.
The advisory traces the cause to two internal functions that read status lines and key listings from gpg. Each reallocates its buffer when more space is needed but writes the new pointer back to the context only at the end of the function. An early return on a read error leaves a stale pointer to freed memory, which is freed a second time on release.
Johan Carlsson found the bug, and GitLab informed GnuPG on November 12. Disclosure was planned for November 25 and moved to November 20 because the Ruby2Shell bug forced GitLab to update earlier.
Any software using a GPGME version before 2.3.0, as a shared library, a DLL or a statically linked copy, is affected. GnuPG lists Gpg4win, GnuPG Desktop, GnuPG VS-Desktop, most mail clients, many XMPP clients, Samba and Flatpak. Update the shared library to 2.3.1, or take the DLL from Gpg4win 5.1.2. Statically linked binaries must be rebuilt against 2.3.1, and the advisory attaches a patch for older versions that cannot move.
In our reading, bundled copies are the part that lingers. A system library update does not reach an application that carries its own GPGME, so a patched laptop can still run a vulnerable mail client. The same shape appeared in Java4Shell and the NGINX HTTP/2 flaw. List the applications that embed GPGME, ask each vendor for a rebuilt release, and start with mail clients.