Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsNews Explainer

GPGME Critical Double Free: Update Mail and Signing Software

The GPGME double-free vulnerability affects mail and signing software. See how the flaw works, which builds need attention, and how to verify GPGME 2.3.1.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
22 November 2026
Reading time
6 min read
OpenPGP key moving toward a guarded mail application and repaired software component

The GPGME double-free vulnerability, CVE-2026-129975, affects applications built with vulnerable versions of the OpenPGP integration library. GnuPG disclosed the critical flaw on November 20, 2026, and released GPGME 2.3.1 as the fix. Teams should identify mail and signing software that embeds GPGME, update the library or application, and verify the version actually loaded.

The trigger is a crafted OpenPGP key with an unusually long user ID. GnuPG says the flaw can expose application data, including through signed output. It says remote code execution cannot be ruled out, which is a possibility rather than a demonstrated outcome. The distinction matters when prioritizing repairs and describing incident scope.

What Is the GPGME Double-Free Vulnerability?

GPGME is the library that lets applications work with GnuPG. Its advisory identifies two internal functions that read status lines and key listings from gpg. Both start with a buffer and expand it when the data is longer than the original allocation. The defect appears in how the expanded buffer’s pointer is stored.

During reallocation, the functions use the new pointer but update the context object only when they complete. If one returns early, the context can retain a pointer to memory already freed. Releasing that context later frees the same memory again. GnuPG notes that intervening allocations may prevent ordinary allocator checks from detecting the error.

Where the memory error occurs
  1. Crafted OpenPGP keyA long user ID reaches GPGME key handling
  2. Buffer growsThe function uses a new buffer pointer
  3. Early returnThe context can retain the freed pointer
  4. Context cleanupThe same memory can be freed again

This diagram describes the condition in GnuPG’s advisory, not a tested exploit path. A double free can have different effects depending on the application and execution context. GnuPG specifically describes possible data exfiltration and leaves remote code execution as an unresolved possibility.

Which Mail and Signing Applications Need a GPGME Check?

GnuPG says software using a GPGME version earlier than 2.3.0 is affected whether the library is shared, supplied as a DLL, or linked statically. It also says version 2.3.0 was never publicly released. For upstream GPGME releases, 2.3.1 is the fixed target; distributors may backport GnuPG’s patch to an older package, so verify that build against its advisory. Check the version the application uses, rather than the version installed elsewhere on a host.

The advisory lists Gpg4win, GnuPG Desktop, GnuPG VS-Desktop, many mail and XMPP clients, Samba, and Flatpak as examples of GPGME users. An application name alone does not prove an individual installation is vulnerable. Inventory the application build, its bundled libraries, and its update channel before setting its status.

Shared libraries and DLLs may be replaced through a package or application update. A statically linked program must be rebuilt against GPGME 2.3.1, according to GnuPG. Ask the software supplier for the exact GPGME build in each shipped release. Keep the supplier’s answer in the dependency inventory and review it alongside a vulnerability intelligence platform when prioritizing remediation.

GnuPG says GPGMEPP and GPGMEQT do not themselves need updates for this fix. That does not clear an application that also uses a vulnerable GPGME library. Keep the wrapper and the underlying library separate in the inventory. The decisive question is which GPGME code the running application loads.

What Can the Advisory Establish About Data Loss and Code Execution?

GnuPG says the double free can be used to exfiltrate application data, for example by sending signed data. That describes a potential consequence of the defect. It does not identify an affected organization, a successful intrusion, or a measured volume of stolen information. Treat those as incident questions that require local evidence.

The advisory does not present remote code execution as confirmed. Its wording is that such an attack cannot be ruled out. Security teams should therefore prioritize the update without reporting confirmed code execution from this notice alone. The data exfiltration glossary entry helps distinguish the possible exposure of application data from the separate question of code execution.

Brandefense Blackhole recorded 4 dark-chat posts matching GPGME from August 23 through November 21, 2026. The unit is matching posts, not unique authors, incidents, or affected installations. This broad count does not establish discussion of CVE-2026-129975 specifically or active exploitation. Use the vendor’s technical disclosure, rather than conversation volume, to set patch priority.

How Should Teams Verify and Apply the Fix?

First, list software that handles OpenPGP keys or signatures and check its GPGME dependency. Include desktop mail clients, signing tools, server-side integrations, and supplier-managed applications where relevant. Record the installed application release and the GPGME version it actually loads. The vulnerability management guide provides a broader process for keeping that evidence tied to remediation.

Next, update shared-library installations to GPGME 2.3.1. For a Windows DLL, GnuPG says an updated DLL is available with Gpg4win 5.1.2. The same announcement says updated GnuPG Desktop and GnuPG VS-Desktop releases use the fixed library. Confirm the vendor’s supplied application release and loaded library after installation.

For statically linked applications, request or build a release linked against GPGME 2.3.1. A host-level library update will not replace code compiled into a binary. When a library update cannot be applied, GnuPG provides a patch for older versions. Treat that as a supplier-controlled remediation and verify the resulting build rather than assuming the patch applied.

Finally, review relevant application activity if a potentially affected build processed untrusted OpenPGP keys. Preserve the application version, input-handling timeline, errors, and signing or export records available in your environment. Those records can support an incident assessment, but the advisory does not supply a universal detection signature. Do not equate a missing crash with proof that the flaw was never triggered.

Why Did This Notice Arrive Before the Planned Disclosure Date?

GnuPG says it learned of the vulnerability through GitLab on November 12, 2026. The initial coordinated disclosure date was November 25. According to GnuPG, a separate GitLab Ruby2Shell issue prompted an earlier update, and the GPGME notice was published on November 20. The two issues should remain separate in tracking and incident records.

The GPGME 2.3.1 release notes are dated November 19, one day before the advisory’s mailing-list publication. A date difference between a package release and its public explanation does not change the fix target. Document both dates when comparing supplier packages and internal change records. The immediate operational target remains a verified GPGME 2.3.1 build or GnuPG’s supplied patch.

Frequently Asked Questions

Does GPGME 2.3.1 fix CVE-2026-129975?

Yes. GnuPG released GPGME 2.3.1 as the fix and advises an immediate update. Verify that the application loads the fixed library.

Is remote code execution confirmed for this GPGME flaw?

GnuPG says remote code execution cannot be ruled out. Its advisory does not claim a demonstrated remote code execution attack.

Will updating a system GPGME library fix a statically linked application?

No. GnuPG says statically linked binaries must be rebuilt against GPGME 2.3.1. Ask the supplier for a fixed build and verify its dependency.

Sources

  1. GnuPG, Security Advisory for GPGME, November 20, 2026
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →