Loading SecureCyberVM…
SecureCyberVM
CVE Lookup Daily Threat Briefing Exploited CVEs Ransomware Zero-day
SecureCyberVM
Get the Patch Brief

GnuPG fixes critical GPGME double free CVE-2026-129975 triggered by malicious keys

GnuPG has released GPGME 2.3.1 to fix CVE-2026-129975, a critical double free that a crafted OpenPGP key can trigger to exfiltrate application data. Remote code execution has not been ruled out.

GnuPG fixes critical GPGME double free CVE-2026-129975 triggered by malicious keys

The GnuPG project has released GPGME 2.3.1 to fix a critical double free, tracked as CVE-2026-129975, in the library that applications use to talk to GnuPG. According to the project’s security advisory, an OpenPGP key carrying a crafted, very long user ID can trigger the bug, which can be used to exfiltrate data from an affected application, for example by sending it signed data.

The advisory says every version of GPGME before 2.3.0 is affected, and version 2.3.0 was never publicly released, so in practice 2.3.1 is the first fixed release. GnuPG says remote code execution cannot be ruled out and urges an immediate update. No exploitation in the wild has been reported.

What happened

GPGME is the standard programming interface that mail clients, chat clients and other software use to call GnuPG for encryption, decryption, signing and key handling. According to the advisory, the flaw sits in two internal routines that read status lines and key listings returned by the gpg process. The project’s write-up and reporting by The Hacker News identify them as read_status() and read_colon_line().

Both routines start with a 1,024-byte buffer and reallocate it when input runs longer. The new buffer address is only written back to the context object when the function finishes normally. If the function exits early, for example on a read error, the context keeps a stale pointer to memory that has already been released, and that memory is freed a second time when the context is torn down. GnuPG notes that other allocations in between mean common allocator double-free checks may not catch the condition.

The bug was found by Johan Carlsson and reported to the project by GitLab on 12 November, according to the advisory. Coordinated disclosure had been planned for 25 November but was brought forward to 20 November because GitLab had to ship an earlier update in response to the separate Ruby2Shell vulnerability. The fix appears in the GPGME 2.3.1 changelog dated 19 November.

Who is affected

The advisory states that all software using a GPGME version prior to 2.3.0 is affected, whether the library is loaded as a shared library, a Windows DLL, or statically linked. GnuPG lists the following as examples of software that uses GPGME:

  • Gpg4win, GnuPG Desktop and GnuPG VS-Desktop
  • Most mail clients
  • Many XMPP clients
  • Samba
  • Flatpak

The project says the C++ and Qt bindings, GPGMEPP and GPGMEQT, do not need to be updated. The advisory does not enumerate which specific mail or chat clients process attacker-supplied keys automatically, and The Hacker News notes that the advisory does not say which programs pass such material to the library without a manual key import. Exposure in a given product therefore depends on how it handles incoming keys and signed content.

Severity and exploitation

GnuPG classifies the issue as a critical security bug. The project states that the double free can be used to exfiltrate application data and that remote code execution cannot be excluded, but it has not published proof-of-concept code. As of publication, neither the project nor The Hacker News reported any attacks exploiting the flaw.

The trigger is attacker-controlled input in the form of an OpenPGP key, which is the kind of material encrypted-mail and messaging software routinely receives from outside parties. That raises the practical risk for clients that parse keys or signatures from untrusted senders.

What defenders should do now

  1. Inventory systems and applications that use GPGME, including mail clients, XMPP clients, Samba deployments, Flatpak installations and Gpg4win or GnuPG Desktop installs.
  2. Update the system GPGME shared library to version 2.3.1 through the GnuPG project or your distribution’s security updates as they become available.
  3. On Windows, update to Gpg4win 5.1.2, which bundles the fixed library; GnuPG says the DLL can also be taken from that release.
  4. For branches that cannot move to 2.3.1, apply the patch attached to the advisory, which the project says should apply to very old versions, or use the fixed legacy 1.24.4 release referenced by The Hacker News.
  5. Identify applications that bundle or statically link GPGME. Updating the system library does not fix these; they need vendor rebuilds against 2.3.1, so track vendor advisories and request timelines.
  6. Until patches are in place, treat unsolicited OpenPGP keys and signed messages from unknown senders with extra caution, and monitor encryption-capable clients for unexpected crashes, which may indicate attempts to trigger memory corruption.

SCVM analysis

GPGME is a dependency rather than a product, which makes this flaw harder to track than a typical vendor patch. Many organizations will not see GPGME in their asset inventory at all; it arrives inside mail clients, desktop encryption suites, file servers and sandboxed application runtimes. The advisory’s warning about static linking matters most here: patching the operating system package closes only part of the exposure, and the remainder depends on third-party rebuild cycles that may take weeks.

The absence of an interim workaround and the possibility of code execution argue for treating this as a priority update on endpoints that handle encrypted mail or messaging, even without evidence of exploitation. Software composition analysis and SBOM data, where available, are the most reliable way to find embedded copies.

Sources

About this article: produced by the SCVM Newsroom with AI assistance from the public sources linked above, enriched with NVD, FIRST EPSS and CISA KEV data, and checked by automated quality controls under our editorial policy. Spotted an error? Request a correction.

SecureCyberVM

Install SecureCyberVM

Get the Daily Threat Briefing and exploited-CVE alerts one tap away, full screen, like an app.