Skip to content
All posts

GPGME CVE-2026-129975: GnuPG Double Free, Update to 2.3.1

November 22, 2026 · Team PlayCISO
TL;DR · the short version

GnuPG published a security advisory on 20 November 2026 for CVE-2026-129975 (T8557), a double free in GPGME, the library most applications use to call GnuPG. A crafted OpenPGP key with a very long user ID can trigger it: two internal functions reallocate a 1024-byte buffer and, on an early return, lose the new pointer, so the memory is freed twice. GnuPG calls it critical, says it can be used to exfiltrate data from applications and that remote code execution cannot be ruled out. All versions before 2.3.0 are affected, including statically linked copies; the advisory names Gpg4win, GnuPG Desktop, most mail clients, many XMPP clients, Samba and Flatpak. Fixed in GPGME 2.3.1 and legacy 1.24.4; Gpg4win 5.1.2 includes the fix. No exploitation has been reported. Johan Carlsson found it; GitLab reported it to GnuPG on 12 November.

Put it into practice
Put GPGME in your patch queue with a reason
Score it by exposure and impact: mail and chat clients that parse keys from strangers come first.
Open the prioritizer

GnuPG says a crafted OpenPGP key can trigger a double free in GPGME, the library behind GnuPG support in most mail clients, and asks everyone to update now. The advisory, posted by Werner Koch on 20 November 2026, covers CVE-2026-129975 (T8557) in every GPGME release before 2.3.0. GnuPG says it can be used to exfiltrate data from applications and that remote code execution "can't be ruled out". The fix is in GPGME 2.3.1 and, on the legacy branch, 1.24.4. No exploitation has been reported.

Who this is for: security and IT leaders whose staff use encrypted email (Thunderbird-style clients, KMail, Gpg4win on Windows), Linux platform owners, and anyone who ships software that links GPGME statically.

Based on GnuPG's advisory, GPGME's NEWS files and the gnupg.org download listing, read on 22 November 2026. The CVE.org record had not been published yet. PlayCISO is not affiliated with the GnuPG project. We publish no exploit details.

Confirmed vs not yet known

GnuPG confirms (20 Nov): a double free in GPGME triggered by a crafted OpenPGP key with a very long user ID; "all versions prior to 2.3.0" affected, as a shared library, DLL or statically linked; fixed in 2.3.1 (and 1.24.4 per its NEWS file); Gpg4win 5.1.2 includes the fix; a patch for older versions is attached.

GnuPG's impact statement: the bug "can be used exfiltrate data from applications by sending for example signed data"; RCE "can't be ruled out".

Not established: any exploitation in the wild, a public proof of concept, a CVSS score (no CVE.org record yet), and which distribution packages and application versions carry the fix. GnuPG warns that the 1.24 legacy branch may not get every future security patch.

Who is affected

GPGME sits between applications and the gpg program. The advisory names these as examples of software that uses it:

  • Gpg4win, GnuPG Desktop and GnuPG VS-Desktop
  • "most mail clients" and many XMPP clients
  • Samba and Flatpak

The trigger is a crafted key, so any program that imports or lists keys it receives (from an email, a keyserver, a chat contact or a package repository) is the place to look first. The advisory does not say whether a user has to take any action, such as importing the key, for the bug to fire.

Fixed versions

ComponentFixed inSource
GPGME (current)2.3.1 (2.3.0 was never publicly released)GnuPG advisory, NEWS
GPGME (legacy 1.x branch)1.24.4NEWS on gpgme-1.24.4, gnupg.org
Gpg4win5.1.2GnuPG advisory, gpg4win.org
Statically linked programsRebuild against 2.3.1GnuPG advisory
GPGMEPP, QGpgME (C++ and Qt bindings)No update neededGnuPG advisory

The 1.24.4 readme says the branch was created before the bindings were split out and "We can't guarantee that it will see all security patches", so treat 1.24.4 as a stopgap and plan the move to 2.x.

Useful next, if this was relevant to you

Showing 1 of 3: CISO Readiness Scorecard

Timeline

DateEventSource
12 Nov 2026GitLab informs GnuPG of the bug, found by Johan CarlssonGnuPG advisory
18 Nov 2026GPGME 2.3.0 tagged with the fix (not publicly released, per GnuPG)GPGME NEWS
19 Nov 2026GPGME 2.3.1 dated ("Fix a regression in 2.3.0")GPGME NEWS
20 Nov 2026Advisory published; 2.3.1 and 1.24.4 tarballs on gnupg.org; Gpg4win 5.1.2 named as fixedGnuPG advisory, gnupg.org
25 Nov 2026Originally planned disclosure date, brought forward because GitLab had to update earlier for Ruby2ShellGnuPG advisory

What security leaders should do this week

  • Update Windows endpoints that run Gpg4win to 5.1.2. It is the easiest win and the advisory names it directly.
  • Patch Linux hosts and desktops as distribution packages arrive. Look for libgpgme / gpgme packages at 2.3.1, 1.24.4 or a backported fix that cites CVE-2026-129975. Prioritise mail and chat clients, Samba servers and Flatpak hosts.
  • Ask your software suppliers about static builds. Any product that bundles GPGME statically stays vulnerable until it is rebuilt. Put the question in this week's vendor touchpoints.
  • Check your own build pipeline. If your teams link GPGME into containers or appliances, rebuild against 2.3.1, or apply GnuPG's patch for older trees.
  • Score and record it. With no CVSS yet, use the SSVC calculator to decide urgency, rank it with the vulnerability prioritizer, and log any system you cannot update in your risk register with an owner and a date.

The early disclosure is tied to Ruby2Shell (CVE-2026-132825), which also needed fast patching this week. For the vendor view, see GnuPG in the Breach Index. CVE-2026-129975 is a vulnerability in GPGME, not a breach of GnuPG.

Frequently asked questions

What is CVE-2026-129975?

CVE-2026-129975 (GnuPG task T8557) is a double free in GPGME, the library most applications use to talk to GnuPG. GnuPG's 20 November 2026 advisory calls it a critical security bug: a crafted OpenPGP key with a very long user ID can trigger it. Two internal functions that read gpg's status lines and key listings start with a 1024-byte buffer and reallocate it as needed; on an early return such as a read error, the new pointer is not saved, so the memory is later freed twice.

Which GPGME versions fix CVE-2026-129975?

GPGME 2.3.1 (dated 19 November 2026) and, for the legacy 1.x branch, GPGME 1.24.4 (20 November 2026). Both NEWS files list "Fix a double free in the status line read code. [T8557,CVE-2026-129975]". The advisory says 2.3.0 was never publicly released. Gpg4win 5.1.2 ships the fixed library. Statically linked programs must be rebuilt.

Which software is affected by the GPGME double free?

The advisory says all GPGME versions before 2.3.0, whether used as a shared library, a DLL or statically linked. It names Gpg4win, GnuPG Desktop, GnuPG VS-Desktop, most mail clients, many XMPP clients, Samba and Flatpak as examples. It does not list individual distribution packages or application versions.

Is CVE-2026-129975 being exploited?

No exploitation has been reported in the sources we read. GnuPG says the double free "can be used exfiltrate data from applications by sending for example signed data" and that a remote code execution attack "can't be ruled out", and asks everyone to update immediately.

Do I need to update GPGMEPP or QGpgME?

No, according to the advisory: the C++ and Qt bindings (GPGMEPP and GPGMEQT) do not need updating. The fix is in the C library.

What if I cannot update GPGME?

GnuPG attached a patch to its advisory that it says solves the bug for older versions and should apply cleanly even to very old releases. Use it to rebuild, or take your distribution's patched package when it ships.

Who found CVE-2026-129975 and why was it disclosed early?

GnuPG credits Johan Carlsson. GitLab told GnuPG about it on 12 November 2026. Disclosure was planned for 25 November but moved to 20 November because GitLab had to update earlier because of the separate Ruby2Shell bug.

Is this a breach of GnuPG?

No. It is a vulnerability in GPGME software, not a breach of the GnuPG project.

Sources

Put GPGME in your patch queue with a reason
Score it by exposure and impact: mail and chat clients that parse keys from strangers come first.
Open the prioritizer
Take this with you
Who is affected · Fixed versions · Timeline · What security leaders should do this week · Sources

Ready to practise the decisions these articles describe?

Run your first Cyber War Room free →

Pro