Skip to content
GnuPG releases GPGME 2.3.1 to fix critical double-free vulnerability

GnuPG releases GPGME 2.3.1 to fix critical double-free vulnerability

News.Lavx.Hu • November 21, 2026

GPGME 2.3.1 fixes CVE-2026-129975, a critical double-free vulnerability triggered by a crafted OpenPGP key with a user ID of unusual length; the advisory does not rule out remote code execution.

Werner Koch and the GnuPG project published GPGME 2.3.1 on Nov. 19, 2026. 'This version fixes a critical security bug found in all prior versions,' Koch said in the announcement.

The advisory carries internal ID T8557 and CVE-2026-129975. Johan Carlsson discovered the vulnerability, and GitLab informed the project on Nov. 12, 2026. The project set Nov. 25, 2026, for coordinated disclosure, then moved the date to Nov. 20, 2026, after GitLab moved its own disclosure earlier because of the Ruby2Shell bug.

An attacker can trigger the bug by using an OpenPGP key that contains a crafted user ID of unusual length. An attacker can use the resulting double free to exfiltrate data from applications by sending signed data. The advisory does not rule out remote code execution. The advisory calls for an immediate update.

The root cause sits in two GPGME internal functions that read status lines and key listings from gpg. Each function allocates a 1,024-byte buffer and reallocates it when more space is required. The function uses the pointer to the new buffer, but assigns it back to the context object only at the end. If the function returns early on a read error or another event, the context keeps a stale pointer to freed memory. When the context is released, that memory is freed a second time. Allocations between the two frees can prevent allocator checks from catching the double free.

All software that uses GPGME before version 2.3.0 faces the bug, whether the library ships as a shared library, a DLL, or a statically linked binary. Affected software includes Gpg4win, GnuPG Desktop, GnuPG VS-Desktop, most mail clients, many XMPP clients, Samba and Flatpak.

Update the GPGME shared library to version 2.3.1. Users who need a DLL can take it from the updated Gpg4win release. Rebuild statically linked binaries against GPGME 2.3.1. Older versions can use the patch attached to the advisory. GPGMEPP and GPGMEQT need no update. Version 2.3.1 adds constants GPGME_PK_MLKEM, GPGME_PK_MLDSA and GPGME_PK_DLTHM, with mappings for algorithms used by backends. Read the release information at .

Users can download the GPGME source tarball and its OpenPGP signature from and . The SHA-1 checksum is 1134a407b50204ee6fb9efaa6e1451c2460e543e. Users can download Gpg4win 5.1.2, which includes the fixed GPGME, from . The project publishes Debian-style packages through . Read verification instructions at . The advisory lists the release signing keys at .

Source : [Announce] GnuPG Security Advisory for GPGME (T8557,CVE-2026-129975) , lists.gnupg.org

The full story

This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.

Extracted Entities