Technology1 min read

RCE in Gnupg

By · Published by Everything Blog

In short

The vulnerability, tracked as CVE-2026-129975, involves an improper context update during memory reallocation errors in functions handling status lines and key listings. Attackers can trigger this condition by supplying an OpenPGP key embedded with an exceptionally long user ID to manipulate freed memory. This stale pointer vulnerability compromises any program utilizing the library statically, dynamically, or via DLL. Upstream developers have mitigated the danger with the release of GPGME 2.3.1 alongside updated desktop bundles.

Key points

  • All installations using GPGME library versions prior to 2.3.0 require an immediate upgrad…: All installations using GPGME library versions prior to 2.3.0 require an immediate upgrade to version 2.3.1.
  • Updated packages have also been issued for downstream software including Gpg4win, GnuPG D…: Updated packages have also been issued for downstream software including Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop.
  • Critical tools and applications including Samba, Flatpak, and various email clients are d…: Critical tools and applications including Samba, Flatpak, and various email clients are directly impacted by this flaw.

Sources checked by our analysis pipeline: 1

[Announce] GnuPG Security Advisory for GPGME (T8557,CVE-2026-129975)

Werner Koch

wk at gnupg.org

Fri Nov 20 19:01:51 CET 2026

Hello!

We are pleased to announce the availability of a new GPGME release:

version 2.3.1. This version fixes a *critical security bug* found in

all prior versions. We also release a new Gpg4win versions and and

GnuPG Desktop and GnuPG VS-Desktop versions which all make use of GPGME.

Description

===========

By using an OpenPGP key containing a crafted very long user id it is

possible to trigger a double free. This double free can be used

exfiltrate data from applications by sending for example signed data.

Exploiting this bug to mount an Remote Code Execution attack (RCE) can't

be ruled out. Thus an immediate update is highly suggested.

Our internal ID is T8557 (https://static.dev.gnupg.org/T8557)

The CVE-id is CVE-2026-129975.

This vulnerability was discovered by Johan Carlsson and we were informed

by GitLab on 2026-11-12. Initially we set 2026-11-25 for a coordinated

disclosure; due to the new Ruby2Shell bug GitLab had to update earlier

and thus we also disclosed the GPGME bug on 2026-11-20.

Technology