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

GPGME Double Free and Data Exposure (CVE-2026-129975)

CVE-2026-129975 is a double-free flaw in GPGME, the library used by applications that process OpenPGP material.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-129975
Vendor
GnuPG
Affected Product
GPGME library and applications using it
Exploitation
Not confirmed
Published
2026-11-20

GnuPG says a crafted key with an unusually long user ID can trigger it. The vendor warns that the flaw could expose application data; it cannot rule out remote code execution.GnuPG announced the fix on 20 November 2026 and urges an immediate update. These are potential outcomes described by the vendor. Organizations should identify applications that bundle or link GPGME before deciding which deployments need remediation.

What it allows

How Can CVE-2026-129975 Expose Application Data?

GnuPG traces the flaw to internal handling of status lines and key listings. When a buffer grows, an early return can leave the context holding an obsolete pointer. Later cleanup can free that memory again. A crafted OpenPGP key with a very long user ID can reach this condition.

The vendor says the double free can be used to exfiltrate data from an application, for example through signed data. It also says remote code execution cannot be ruled out. These are potential outcomes in the advisory, not evidence that either outcome has occurred in an organization.

Brandefense Blackhole counted two dark-chat posts matching CVE-2026-129975 from 23 August through 21 November 2026. The measured unit is matching posts, and this count is an internal research signal. It does not establish an incident, successful exploitation or a victim.

Prioritize the affected library copies in a Vulnerability Intelligence workflow. Record each application's running GPGME version and its linkage type so the fix can be verified against the actual deployment.

Who is affected

Which GPGME Versions Are Affected?

GnuPG says software using GPGME as a shared library, DLL or static dependency is affected. Its impact section names versions before 2.3.0, while its release announcement says the bug affects all releases before 2.3.1. The same notice says 2.3.0 was never publicly available.

For upstream GPGME releases, versions before 2.3.1 require the fix. A distributor may backport GnuPG's patch to an older package, so verify that build against the distributor's advisory.

The advisory names Gpg4win, GnuPG Desktop, GnuPG VS-Desktop, mail clients, XMPP clients and other GPGME users as examples. Inclusion depends on the GPGME version actually shipped or linked by the application. Check bundled DLLs and statically linked binaries separately from system shared libraries. Include this dependency inventory in vulnerability management.

GnuPG says GPGMEPP and GPGMEQT do not themselves need updating. An application using either binding still needs its underlying GPGME dependency checked. Keep the application, dependency and running-version evidence together in the patch management process.

Timeline

  1. 2026-11-12

    GnuPG says GitLab informed it of the vulnerability.

  2. 2026-11-19

    GnuPG dates the GPGME 2.3.1 release notes to this day.

  3. 2026-11-20

    GnuPG published the advisory and announced GPGME 2.3.1 and updated desktop packages.

What to do

  1. Inventory GPGME dependencies

    Identify applications using GPGME and record whether each uses a shared library, DLL or static copy. Verify the version deployed with the application.

  2. Update the affected library

    Move shared-library installations to GPGME 2.3.1. For a bundled DLL, use the corrected package supplied by the application vendor or the updated Gpg4win package where appropriate.

  3. Rebuild static applications

    Rebuild statically linked binaries against GPGME 2.3.1. Where a full upgrade is unavailable, consult GnuPG's advisory for its older-version patch option.

  4. Confirm the running dependency

    After deployment, verify each affected application loads or contains the corrected GPGME build. Record the result for each application rather than treating a package download as proof of remediation.

What Brandefense can do

Frequently Asked Questions

Can CVE-2026-129975 lead to remote code execution?

GnuPG says remote code execution cannot be ruled out. Its advisory specifically describes possible application-data exfiltration through the double-free flaw.

Does updating a system GPGME package fix every application?

It addresses applications using that updated shared library. Bundled DLLs and statically linked applications need their own corrected GPGME copy or a rebuilt binary.

Which version fixes the GPGME double free?

GnuPG released GPGME 2.3.1 as the fix. It also released Gpg4win 5.1.2 with the corrected GPGME library.

Sources

  1. GnuPG Security Advisory for GPGME (T8557, CVE-2026-129975)GnuPG
ShareLinkedInX
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 →