Skip to content
TrustList
Security advisories

GPGME 2.3.1 fixes a critical double free reachable through a crafted OpenPGP key

Editorial

By TrustList Editorial

GnuPG released GPGME 2.3.1 on 20 November 2026 to fix CVE-2026-129975, a double free triggered by a key with a very long user ID; Gpg4win, GnuPG Desktop, most mail clients and Samba use the library.

About GPGME 2.3.1 fixes a critical double free reachable through a crafted OpenPGP key

GPGME 2.3.1 fixes a critical double free reachable through a crafted OpenPGP key

20 November 2026: The GnuPG project has released GPGME 2.3.1 to fix what it calls a critical security bug found in all earlier versions, CVE-2026-129975. GPGME is the library that most applications use to talk to GnuPG, so the fix matters far beyond GnuPG itself: Gpg4win, GnuPG Desktop, GnuPG VS-Desktop, most mail clients, many XMPP clients, Samba and Flatpak are named as users. New builds of Gpg4win, GnuPG Desktop and GnuPG VS-Desktop were released the same day.

Not yet independently verified. The flaw, affected software, fix and timeline come from the GnuPG announcement by Werner Koch of 20 November 2026 (read on 22 November 2026). It gives no CVSS score. The stated impact is data exfiltration; remote code execution is described only as something that cannot be ruled out. We will update this when it can be confirmed, and remove this note.

How the bug works

An OpenPGP key with a crafted, very long user ID can trigger a double free. The fault sits in two internal GPGME functions that read status lines and key listings from gpg. They start with a 1024-byte buffer and reallocate it when more room is needed, but only store the new pointer back in the context at the end of the function. If the function returns early, for example on a read error, the context keeps the stale pointer and the memory is later freed a second time. Because other allocations happen in between, the usual double free checks in memory allocators may not catch it.

The announcement says the bug can be used to exfiltrate data from applications, for example by sending signed data, and that remote code execution "can't be ruled out". It advises an immediate update.

Disclosure brought forward by five days

The flaw was found by Johan Carlsson, and GitLab told the GnuPG project on 12 November 2026. A coordinated disclosure was set for 25 November. Because GitLab had to ship an earlier update for a separate bug, the GPGME disclosure was moved forward to 20 November.

What is affected and what to install

Every program using a GPGME version before 2.3.0 is affected, whether it loads GPGME as a shared library or DLL or has it statically linked. Version 2.3.0 was never released to the public. The fix is:

  • GPGME 2.3.1 (dated 19 November 2026 in its release notes), which also adds constants for the post-quantum ML-KEM and ML-DSA algorithms;
  • for Windows, the GPGME DLL from the updated Gpg4win;
  • for systems that cannot update, a patch attached to the announcement that the project says should apply even to very old versions.

The C++ and Qt bindings, GPGMEPP and GPGMEQT, do not need an update.

Steps for IT and security teams

  • Update Gpg4win, GnuPG Desktop and GnuPG VS-Desktop on managed Windows machines.
  • Apply the GPGME updates from your Linux distribution as they arrive, and check servers that run Samba or mail tools that verify signatures automatically.
  • Ask the vendors of mail clients and other tools that bundle or statically link GPGME when they will ship 2.3.1; static builds stay vulnerable until they are rebuilt.
  • Until then, be wary of importing keys from unknown senders or key servers on unpatched systems.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in