← Back to BLACKWIRE EMBER BUREAU SECURITY ALERT Code snippet showing GPGME double free vulnerability in memory allocation

GPGME 2.3.1 release notes highlight the critical double‑free fix that protects mail, XMPP, and other clients.

GPGME DOUBLE FREE BUG EXPOSES RCE RISK IN MAJOR SOFTWARE

*A critical double‑free flaw in GPGME can exfiltrate data and may enable remote code execution. The GnuPG team released version 2.3.1 on 20 Nov 2026 to seal the hole. Immediate updates are essential.*

By EMBER Bureau - BLACKWIRE  |  November 21, 2026, 17:00 CET  |  GPGME, CVE-2026-129975, remote code execution, double free, security update

On 20 November 2026 the GnuPG project released GPGME 2.3.1, a critical patch for a double‑free flaw that lurked in every prior version. The flaw is triggered by an OpenPGP key with an exceptionally long user ID, causing the library to free the same memory block twice. The announcement warns that the bug can exfiltrate data and that a remote code execution (RCE) attack cannot be ruled out. Discovered by security researcher Johan Carlsson and reported to the GnuPG team via GitLab on 12 November 2026, the issue was slated for coordinated disclosure on 25 November. A separate Ruby2Shell bug forced GitLab to accelerate the timeline, and the advisory went public on 20 November. The internal tracking ID is T8557 and the CVE identifier is CVE‑2026‑129975. The vulnerability resides in two GPGME functions that read status lines and key listings. An initial 1 KB buffer is reallocated when needed, but the context object is only updated after the function completes. Early returns leave a stale pointer, leading to a double free when the context is later released. Memory allocators often miss the double free because intervening allocations mask the error.

How the double free works

The bug originates in two internal GPGME functions that parse status lines and key listings. Each function allocates a 1024‑byte buffer, then reallocates it if the input exceeds that size. When reallocation occurs, the new pointer is used locally but not written back to the context object until the function exits normally. If the function returns early because of a read error or another event, the context retains the stale pointer to the freed memory. Later, when the context is released, the same memory block is freed a second time. Because other allocations intervene, standard double‑free checks in memory allocators may not trigger, allowing the flaw to persist unnoticed.

What systems are vulnerable to the GPGME double free?

All software that links against GPGME versions earlier than 2.3.0 is at risk. The advisory lists Gpg4win, GnuPG Desktop, and GnuPG VS‑Desktop as primary examples. It also names most mail clients, many XMPP clients, Samba, and Flatpak solutions. The vulnerability applies whether GPGME is used as a shared library, DLL, or statically linked binary. Any application that relies on GPGME for OpenPGP operations inherits the double‑free exposure until it is rebuilt or updated to the fixed version.

This double free can be used to exfiltrate data from applications and may enable remote code execution.

How the fix was delivered

GnuPG issued GPGME 2.3.1 on 19 Nov 2026, fixing the double free in the status line read code. Users should replace the shared library with the new version or obtain the updated DLL from Gpg4win 5.1.2, which bundles the patched GPGME. Statically linked binaries must be rebuilt against 2.3.1. For environments that cannot upgrade immediately, a patch attached to the advisory applies cleanly even to very old releases. The release does not require updates to GPGMEPP or GPGMEQT. Debian‑style packages for recent Debian releases are available, and a Windows installer with the fixed library can be downloaded from the Gpg4win site.

What are the broader security implications?

The double free creates a direct path for attackers to extract cryptographic material and potentially execute arbitrary code on vulnerable hosts. Because GPGME underpins email encryption, instant messaging, file sharing, and network authentication, the flaw threatens a wide swath of confidential communications. The advisory’s urgency reflects the difficulty of detecting double‑free exploits in the wild. Rapid deployment of GPGME 2.3.1 is the only reliable mitigation; lingering unpatched installations could become footholds for nation‑state or criminal actors seeking to compromise encrypted traffic.

Frequently asked questions

What is CVE-2026-129975?

CVE-2026-129975 is the identifier for a critical double‑free vulnerability in GPGME that can lead to data exfiltration and possibly remote code execution.

Which applications are affected by the GPGME double free bug?

All software using GPGME prior to version 2.3.0—such as Gpg4win, GnuPG Desktop, GnuPG VS‑Desktop, most mail clients, many XMPP clients, Samba, and Flatpak—are vulnerable.

How can users protect themselves from this vulnerability?

Update the GPGME shared library to version 2.3.1, use the updated Gpg4win 5.1.2 DLL, rebuild statically linked binaries against 2.3.1, or apply the provided patch for older versions.

The window for safe operation is closing fast. Organizations that rely on GPGME must verify that every component—whether a shared library, DLL, or statically linked binary—runs version 2.3.1 or later. Delays increase exposure to data theft and possible remote takeover. The GnuPG team's swift disclosure and patching demonstrate the high stakes of open‑source cryptographic infrastructure, but the onus now lies with administrators to act without hesitation.

Sources: Hacker News announcement, GnuPG mailing list (https://lists.gnupg.org/pipermail/gnupg-announce/2026q4/000517.html)