
November 21, 2026 – GnuPG has released GPGME 2.3.1 to fix a critical double-free vulnerability, tracked as CVE-2026-129975 (internal ID T8557). An attacker can trigger the bug with a specially crafted OpenPGP key that has an unusually long user ID. Exploitation could expose data from the affected application, and the project says it cannot rule out remote code execution. GnuPG urges users to update immediately.
What happened
Johan Carlsson discovered the flaw, and GitLab informed the GnuPG project on November 12. The team originally planned coordinated disclosure for November 25. It moved the date up to November 20 after GitLab brought forward its own disclosure because of the Ruby2Shell issue. GPGME 2.3.1 is dated November 19 and was announced on November 20, alongside updated Gpg4win and GnuPG Desktop builds.
How the bug works
The problem sits in two internal GPGME functions that read status lines and key listings from gpg. When a very long user ID passes through these code paths, memory ends up being freed twice, once during processing and again when the engine is cleaned up. An attacker could exploit this by delivering the malicious key to an application that uses GPGME, for example through signed data.
Who is affected
Every public GPGME release before 2.3.1 is vulnerable, whether it is installed as a shared library, a Windows DLL, or statically linked into an application. GnuPG’s advisory describes the affected range as versions prior to 2.3.0, but 2.3.0 was never publicly released. GPGME is widely embedded, so the exposure includes email clients, Samba, Flatpak packages and Windows systems running Gpg4win.
What to do
- Shared libraries / DLLs: Upgrade to GPGME 2.3.1
- Windows (Gpg4win): Update to Gpg4win 5.1.2, which bundles GPGME 2.3.1
- Statically linked or bundled apps: Rebuild and redeploy against GPGME 2.3.1
- Legacy branch: Move to GPGME 1.24.4, released November 20 with the same fix
- Cannot upgrade: Apply the official patch attached to the T8557 ticket, which GnuPG says should apply cleanly even to very old versions
The patch was not attached to the original announcement email, so look for it on the T8557 ticket rather than in the mailing list post.
Bottom line
Audit where GPGME lives in your stack, including copies bundled inside third-party applications, and patch before untrusted OpenPGP keys reach those systems. Vendors that ship GPGME statically will need to release rebuilt versions, so check for updates from those vendors as well.
Sources:

Leave a Reply