Overview
- The GnuPG project disclosed the vulnerability and published GPGME 2.3.1 and Gpg4win 5.1.2 to deliver the fix after announcing the issue on Friday, November 20.
- The bug, tracked as CVE-2026-129975 and discovered by Johan Carlsson, stems from two internal reader routines that reallocate buffers and can leave a stale pointer that is freed twice.
- Any software using GPGME before version 2.3.0 is vulnerable whether the library is a shared lib, a Windows DLL, or statically linked into an application, with examples including mail and XMPP clients, Samba, GnuPG Desktop, and Gpg4win.
- Fixing the problem often requires more than updating a system library because programs that bundle or statically link GPGME must be rebuilt or repackaged; the project also supplied a patch and a legacy-branch release (1.24.4) for older installs.
- No public exploits have been reported so far but the project warns remote code execution cannot be ruled out and urges users, packagers, and distributions to update immediately to prevent data leaks and further downstream risk.