CVE-2026-129975: GPGME Double-Free Flaw Affects Versions Before 2.3.0

Summary
GnuPG says a malicious OpenPGP key with a long user ID can trigger a double free in GPGME before 2.3.0. No exploitation has been reported; remote code execution cannot be ruled out. GPGME 2.3.1 fixes the flaw.
Key points
- CVE-2026-129975 affects software using GPGME versions before 2.3.0, including shared-library, DLL and statically linked deployments.
- A malicious OpenPGP key with an unusually long user ID can trigger a double free in read_status() and read_colon_line().
- The flaw could expose data from affected applications; the advisory says remote code execution cannot be ruled out.
- The GnuPG project has not reported attacks exploiting the flaw.
- GPGME 2.3.1 is the fixed release; the project says version 2.3.0 was never publicly available.
- The advisory provides no interim workaround for software that cannot be updated.
Article Details
- Vulnerability Types
- Double free
- Severity
- Critical
- Affected Versions
- GPGME versions before 2.3.0
- Exploitation Status
- not_reported
- Exploit Availability
- unknown
- Patch Status
- available
CVE
People
Products
GnuPG DesktopExamples the project gives include most mail clients, many XMPP clients, Samba, and its own Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop packages.GnuPG VS-DesktopExamples the project gives include most mail clients, many XMPP clients, Samba, and its own Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop packages.Gpg4winExamples the project gives include most mail clients, many XMPP clients, Samba, and its own Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop packages.GPGMEA malicious OpenPGP key with an unusually long user ID can trigger a critical memory bug in GPGME, the standard library that programs use to work with GnuPG.
