
GnuPG releases fix for critical GPGME double-free flaw CVE-2026-129975
GnuPG released GPGME 2.3.1 to fix CVE-2026-129975, a double-free bug triggered by malicious OpenPGP keys with long user IDs. The flaw affects many applications that use GPGME, including mail clients, XMPP clients, Samba and Gpg4win, and can expose application data. Because statically linked copies require separate rebuilt releases, patching depends on each product rather than only the system library.
GnuPG warned of a critical flaw in GPGME, the library applications use to talk to GnuPG. The bug, CVE-2026-129975, is a double-free error that can be triggered when a malicious OpenPGP key contains an unusually long user ID. It affects GPGME versions before 2.3.0, whether used as a shared library, a Windows DLL, or statically linked into software. The project said fixed versions are available and gave examples including mail clients, XMPP clients, Samba, Gpg4win and GnuPG desktop packages.
The project's advisory says the defect sits in read_status() and read_colon_line(), routines that process status lines and key listings returned by GnuPG. When input is too long, the code moves it to a larger buffer but records the new address only if the operation finishes without errors. An error between those steps can leave a pointer to memory already freed, causing cleanup to free it again. The bug was found by Johan Carlsson and reported through GitLab, with disclosure moved up after another issue forced earlier updates.
GPGME is not a niche utility: it is a common bridge between software and GnuPG's OpenPGP implementation. That places it under mail, messaging, file-sharing and credential tooling, so a single library defect can spread across many products. The advisory notes no known exploitation and says remote code execution cannot be ruled out. It also warns that updates to a system library do not fix bundled or statically linked copies, meaning each affected application must ship its own rebuilt release.
The stakes are concentrated in software that accepts signed or key-related data and passes it to GPGME without manual import, a path the advisory cites as an example but does not fully enumerate. Users and administrators of Gpg4win, mail clients, XMPP clients, Samba deployments and other GPGME-based tools should update to GPGME 2.3.1, Gpg4win 5.1.2 or the legacy 1.24.4 branch where applicable. The project provides no interim workaround for products that cannot update yet.
It affects a common encryption bridge used by mail, messaging and file-sharing tools, so one library bug can expose data across many products. Users and admins must update GPGME or the specific applications that bundle it.
Sources (1)
- [1]Original source(https://thehackernews.com/2026/11/gnupg-warns-critical-gpgme-flaw-could.html)