The GnuPG project has shipped emergency fixes for a critical memory-safety defect in GPGME, the library that lets applications talk to GnuPG, warning that a deliberately crafted OpenPGP key can corrupt memory and potentially expose data held by affected programs.
The bug, tracked as CVE-2026-129975, affects every release of GPGME prior to 2.3.0, regardless of whether the library is loaded as a shared object, a Windows DLL or statically compiled into an application. The fixed release is GPGME 2.3.1, published this week; a version 2.3.0 was never made publicly available.
At the root of the problem is a double free, in which the same block of memory is released twice. Two internal routines, read_status() and read_colon_line(), read status lines and key listings returned by gpg. They start with a 1024-byte buffer and enlarge it when input runs long, but the pointer to the new buffer is written back to the context object only at the end of the function. If the routine exits early on a read error or similar event, the context keeps a dangling pointer to freed memory, and cleanup later frees it a second time. Intervening allocations can mask the fault from the usual double-free checks built into memory allocators.
GnuPG lead developer Werner Koch said the flaw could be weaponized. "By using an OpenPGP key containing a crafted very long user id it is possible to trigger a double free. This double free can be used exfiltrate data from applications by sending for example signed data," he wrote in an announcement. "Exploiting this bug to mount an Remote Code Execution attack (RCE) can't be ruled out. Thus an immediate update is highly suggested."
The project said it has seen no attacks exploiting the defect so far. Its illustration of an attack path involves signed data delivered to an application; the advisory does not specify which programs hand such material to the library without a manual key import.
The exposure is broad because GPGME underpins a large of the software world's encryption plumbing. The project lists most mail clients, many XMPP clients, Samba, Flatpak and its own Gpg4win, GnuPG Desktop and GnuPG VS-Desktop packages among the affected users.
Note: The legacy branch's own release notes state that the project cannot guarantee every security patch will land there.
Updating a system-wide shared library is not sufficient for applications that carry their own statically linked or bundled copy of GPGME, since those builds must be recompiled and reissued by the vendors that ship them. The advisory offers no interim workaround for software that cannot be updated yet.
Johan Carlsson identified the flaw, and GitLab reported it to the project last week. Disclosure had been scheduled for November 25 but was moved forward after the newly emerged Ruby2Shell bug forced an earlier round of updates, according to the advisory.
The timing puts pressure on maintainers of downstream projects. Mail and messaging clients that link GPGME are the most visible risk surface, because they routinely parse keys and signatures supplied by outside parties, and a single malformed user ID is enough to reach the faulty code path. Enterprise Linux and BSD distributions that package GPGME will need to backport the fix or the supplied patch to their supported branches, while Flatpak's runtime and application bundles will require rebuilt releases to pick up the corrected library. Administrators running Gpg4win on Windows face the simplest path, a straight upgrade to version 5.1.2.
Once added, BigGo Finance appears first in Google Top Stories, so you get the broadest, most up-to-the-minute, and most comprehensive global financial news first.
