GPGME 2.3.1 patches critical double-free flaw tracked as CVE-2026-129975
GnuPG has released GPGME version 2.3.1 to fix a critical vulnerability in all prior versions, alongside updated Gpg4win, GnuPG Desktop and GnuPG VS-Desktop builds that depend on the library. A specially crafted OpenPGP key with an abnormally long user ID can trigger a double free, allowing data exfiltration through signed data and potentially remote code execution. Researcher Johan Carlsson reported the flaw, and disclosure was moved up to November 20, 2026 after GitLab needed to patch an unrelated bug sooner than planned.
GoKawiil's interpretation of the reporting above, not reported fact.
Because GPGME underlies many mail clients and encryption tools, the flaw's reach extends far beyond GnuPG's own software, meaning any application linking the vulnerable library—statically or dynamically—could be exposed. GnuPG's advisory says RCE exploitation cannot be ruled out, which raises the stakes for organizations relying on signed or encrypted communications. The root cause, a stale pointer left after buffer reallocation, suggests the bug could persist quietly in software that hasn't been updated, making rapid patching important.
- GPGME 2.3.1 fixes a critical double-free bug affecting all earlier versions.
- A malicious OpenPGP key with a long user ID can trigger the flaw, possibly enabling RCE.
- Gpg4win, GnuPG Desktop, GnuPG VS-Desktop and many mail clients need updating.
Source: lists.gnupg.org, 2026-11-21
Published there as: “RCE in Gnupg”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.