A crafted OpenPGP key can trigger a double free in GPGME, and RCE can't be ruled out

RCE in Gnupg

GnuPG released GPGME 2.3.1 to fix a critical double-free bug (CVE-2026-129975, tracked as T8557) present in every earlier version. A malicious OpenPGP key with an oversized user ID corrupts a stale buffer pointer, letting attackers exfiltrate data from applications and possibly achieve remote code execution. Nearly everything linking GPGME is affected — mail clients, XMPP clients, Samba, Flatpak, Gpg4win, and GnuPG Desktop. An immediate update is strongly advised.

Exploiting this bug to mount a Remote Code Execution attack (RCE) can't be ruled out. Thus an immediate update is highly suggested.
  1. uptrails

    Reportedly fixed by Red Hat 5 years ago based on the output from conventional tools, but missed by upstream: https://gitlab.com/redhat/centos-stream/rpms/gpgme/-/blob/c9...

  2. miduil

    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.

    I guess pretty important for GitLab since it supports signed commits, code execution in that path is pretty bad.

    You can find the GitLab Omnibus related patch here: https://gitlab.com/gitlab-org/omnibus-gitlab/-/commit/279ac3...

  3. mik1998

    It's a double free bug, not an RCE chain. Are these vulnerability reports intentionally overstated?

  4. usr1106

    What are practical attack vectors for Linux workstations and servers?

    The masses of internet users don't know what GPG is. I'd caim the majority of software developers don't have a GPG key and never explicitly verify any signature.

    But packages of many distros are verified using GPG. Is the vulnerable component involved or not?

  5. mmsc

    The vulnerability is in GpgME (the library), not GnuTLS (the library).

More from this day

2026-11-21