GPGME: crafted OpenPGP user ID triggers double free, possible data exfiltration/RCE (CVE-2026-129975)
Severity: critical · Patch status: patched · Since 2026-11-20 · CVE-2026-129975
GnuPG released GPGME 2.3.1 on 2026-11-19 and announced it on 2026-11-20, together with Gpg4win 5.1.2 and new GnuPG Desktop and GnuPG VS-Desktop builds, to fix CVE-2026-129975, which GnuPG rates critical. An OpenPGP key with a very long user ID can trigger a double free in GPGME's read paths for gpg status lines and key listings: a buffer is reallocated, but the context keeps a pointer to the old block until the function returns, so an early error return leaves it pointing at freed memory, which is freed again when the context is released. GnuPG says this can be used to exfiltrate data from applications, for example by getting them to send signed data, and that remote code execution cannot be ruled out. The advisory says all earlier GPGME releases are affected and lists Gpg4win, GnuPG Desktop, GnuPG VS-Desktop, most mail clients, many XMPP clients, Samba and Flatpak as software that uses GPGME. Fix: update the GPGME library and rebuild static binaries against 2.3.1, or apply the patch GnuPG attached to the advisory on older versions. At research time there was no exploitation report and no public proof of concept, and the CVE was not yet in NVD.
What to do
- Immediately update GPGME shared libraries and DLLs to version 2.3.1.
- Rebuild statically linked applications against GPGME 2.3.1.
- Update Gpg4win to 5.1.2 and GnuPG Desktop/VS-Desktop to fixed versions.
- If GPGME cannot be updated, apply the vendor-provided patch to older versions.
- Inventory software embedding GPGME, including mail and XMPP clients, Samba, and Flatpak, and verify fixed versions.
- Treat crafted OpenPGP keys and signed data from untrusted sources with caution until all dependent software is patched.
Fixed versions
Sources
All live incidents on Threat Watch