Skip to content
GnuPG Patches Critical GPGME Double-Free Flaw (CVE-2026-129975)

GnuPG Patches Critical GPGME Double-Free Flaw (CVE-2026-129975)

First seen 21 Nov 2026, 11:47 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 21, 2026 at 17:21 UTC
  • •CVE-2026-129975 is a double-free in GPGME affecting all releases before 2.3.0, however linked.
  • •A crafted OpenPGP key with a very long user ID can trigger it; the project says data exfiltration is possible and RCE cannot be ruled out.
  • •Fixed in GPGME 2.3.1; Gpg4win 5.1.2 bundles the fix and legacy users have 1.24.4.
  • •Statically linked and bundled copies of GPGME require vendor rebuilds, and no interim workaround exists.
  • •The GnuPG project reports no observed exploitation so far.

The GnuPG project released fixes for CVE-2026-129975, a double-free memory bug in GPGME, the library applications use to interface with GnuPG. A deliberately crafted OpenPGP key with an unusually long user ID can trigger the flaw. The project says it could be used to exfiltrate application data and that remote code execution cannot be ruled out, though the articles do not confirm any working RCE. The bug sits in read_status() and read_colon_line(), where an error during buffer reallocation leaves a dangling pointer that is freed a second time. All GPGME releases before 2.3.0 are affected whether used as a shared library, DLL, or statically linked, and the articles name most mail clients, many XMPP clients, Samba, Flatpak, and the Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop packages. GPGME 2.3.1 is the first fixed version, Gpg4win 5.1.2 bundles the fix, and legacy branch users have version 1.24.4, though the legacy notes say the project cannot guarantee every security patch will land there. Statically linked or bundled copies need to be rebuilt by their vendors, and no interim workaround is offered. The project reports no observed exploitation. The bug was found by Johan Carlsson and reported by GitLab; disclosure was moved up from November 25 because of the separate Ruby2Shell bug.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-20
GnuPG issues warning and releases fixed versions
The project published the advisory and fixed GPGME releases; Gpg4win 5.1.2 bundles the fixed library.
Wisevoter
2026-11-25
Originally scheduled public disclosure date
Disclosure was moved forward after the Ruby2Shell bug forced an earlier round of updates.
Thehackernews
Recent
GitLab reports GPGME flaw to GnuPG project
The flaw was found by Johan Carlsson and reported to the project by GitLab last week.
Wisevoter

More articles in this cluster (24)

Following this threat?

Track CVE-2026-129975 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which versions are affected?
All GPGME releases before 2.3.0, whether used as a shared library, Windows DLL, or statically linked. GPGME 2.3.1 is the first fixed version.
Is this being exploited?
The GnuPG project says it has seen no attacks exploiting the flaw so far.
What should we do first?
Update the system GPGME library to 2.3.1 (or Gpg4win 5.1.2 on Windows) and ask vendors to rebuild any bundled or statically linked copies, since system updates do not reach them.