GnuPG Warns of Critical Double-Free Flaw in GPGME Exposing App Data to Malicious OpenPGP Keys

The GnuPG project has disclosed a critical memory corruption vulnerability in GPGME, the standard library used by applications to interface with GnuPG for OpenPGP operations. Tracked as CVE-2026-129975, the flaw is a double-free condition that arises when processing OpenPGP keys containing unusually long user IDs. It affects every version of GPGME prior to 2.3.1, whether the library is used as a shared object, Windows DLL, or statically linked. Impacted software includes most email clients, XMPP clients, Samba, and official GnuPG packages such as Gpg4win. The vulnerability was discovered by Johan Carlsson and reported via GitLab, with disclosure accelerated due to the unrelated Ruby2Shell issue. Fixed releases are now available, and while no in-the-wild exploitation has been observed, remote code execution cannot be ruled out.

The Hacker NewsTranslated from English

Read at source

The GnuPG project has issued a security advisory warning that a malicious OpenPGP key containing an unusually long user ID can trigger a critical memory corruption bug in GPGME, the standard library applications rely on to work with GnuPG.

The flaw, assigned CVE-2026-129975, resides in the read_status() and read_colon_line() routines that parse status lines and key listings returned by GnuPG. When input exceeds expected length, the routines attempt to relocate data into a larger buffer but only update the pointer on successful completion. An intervening error leaves a dangling reference to already-freed memory, resulting in a double-free during cleanup.

All software using GPGME versions before 2.3.1 is affected, regardless of whether the library is loaded dynamically or linked statically. The project explicitly lists mail clients, many XMPP clients, Samba, and its own Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop packages as examples.

No attacks exploiting the issue have been observed so far. The advisory notes that remote code execution cannot be ruled out and gives the example of signed data delivered to an application that passes the material to the library without requiring manual key import.

The vulnerability was found by Johan Carlsson and reported to the project through GitLab last week. Planned disclosure on November 25 was advanced because the unrelated Ruby2Shell bug forced an earlier coordinated update.

What to Update

  • GPGME 2.3.1 is the fixed release; version 2.3.0 was never published.
  • Shared library or DLL users should obtain 2.3.1 from the official project downloads.
  • Windows users should install Gpg4win 5.1.2, which bundles the corrected library.
  • Older branches receive GPGME 1.24.4 as a legacy fix, although the project cannot guarantee future patches on that branch.
  • Applications that bundle or statically link GPGME require separate rebuilt releases; system library updates do not protect them.
  • GPGMEPP and GPGMEQT bindings do not require updates.

No interim workaround is provided for software that cannot be updated immediately.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Vulns & Exploits

Microsoft Entra Connect Health Flaw Exploited to Access Tenant Metadata and Admin Emails
CISA Adds Four Critical Flaws in Apache Roller, Cisco Expressway, SAP NetWeaver, and VMware vCenter to Known Exploited Vulnerabilities Catalog
WhatsApp Patches Three Security Flaws Including Android Bug Suspected in Scam Campaigns