GnuPG releases GPGME fixes for critical OpenPGP memory flaw

GnuPG has released GPGME 2.3.1 to correct CVE-2026-129975, a critical double-free vulnerability in its GPGME library. The flaw can be triggered by a malicious OpenPGP key containing an unusually long user ID and could expose data handled by affected applications. GnuPG also says remote code execution cannot be ruled out.
The issue affects software using GPGME before version 2.3.0, regardless of whether the library is deployed as a shared library, a Windows DLL or a statically linked component. GnuPG has not reported attacks exploiting the vulnerability.
Affected software and delivery models
GPGME is a standard library used by programs that work with GnuPG. The project lists most mail clients, many XMPP clients, Samba, Gpg4win, GnuPG Desktop and GnuPG VS-Desktop among examples of software that may be affected, depending on their GPGME integration.
The deployment model is important for remediation. Updating a system-installed shared library or DLL does not fix an application that contains a bundled or statically linked copy of GPGME. Those products need rebuilt releases from their own maintainers.
GnuPG identifies signed data sent to an application as one possible route to the vulnerable code. Its advisory does not specify which applications process such material without a manual key import, so organisations need to establish how their own mail, messaging and encryption workflows pass OpenPGP data to GPGME.
How the memory error occurs
The defect is in the read_status() and read_colon_line() routines, which process status lines and key listings returned by GnuPG. When input exceeds the current buffer, the routines allocate a larger buffer and move the data.
GnuPG's tracker describes an error path in which the new buffer address is recorded only after the operation completes successfully. If an error occurs before that point, cleanup can retain a pointer to memory already released and free it a second time. This is the double-free condition addressed by the update.
Johan Carlsson found the vulnerability, and GitLab reported it to the project. The disclosure had been scheduled for November 25, but GnuPG said it was brought forward after the Ruby2Shell bug required GitLab to update earlier.
Update guidance
The fixed mainstream release is GPGME 2.3.1; GnuPG notes that version 2.3.0 was never publicly available. Windows users can install Gpg4win 5.1.2, which bundles the corrected library and labels the issue severe.
- Update shared-library and DLL installations to GPGME 2.3.1.
- Use the advisory patch where an immediate upgrade is not possible.
- For the legacy branch, deploy version 1.24.4.
- Request updated releases for products carrying bundled or static GPGME copies.
GPGMEPP and GPGMEQT do not require an update. GnuPG provides no interim workaround for software that cannot yet be patched, and warns that the legacy branch cannot be guaranteed to receive every security patch. Businesses should therefore inventory every GPGME dependency, including embedded copies, apply the appropriate fixed release, and track vendor rebuilds where a system-level update cannot remove the exposure.

