Tag: CVE-2026-129975

  • GPGME 2.3.1 Fixes a Critical Double-Free (CVE-2026-129975)

    GPGME 2.3.1 Fixes a Critical Double-Free (CVE-2026-129975)

    Takeaway: On November 20, 2026, the GnuPG project issued a security advisory for GPGME, the library many programs use to talk to GnuPG. Werner Koch announced GPGME 2.3.1, which fixes CVE-2026-129975, a critical double-free in all prior public versions. The project says a crafted OpenPGP key with a very long user ID can trigger the bug, that the flaw can be used to exfiltrate data from affected applications — for example by sending signed data — and that a remote code execution attack cannot be ruled out. It strongly suggests an immediate update.

    The details below come from that official gnupg-announce message. This article does not reconstruct a proof of concept or describe how to craft such a key. GPGME 2.3.1 is the fixed public release; the advisory notes that version 2.3.0 was never publicly available.

    What the advisory describes

    GPGME is the standard library applications use to work with GnuPG, whether it is loaded as a shared library, a Windows DLL, or statically linked into a program. The bug, tracked internally as T8557 and publicly as CVE-2026-129975, sits in two internal functions that read status lines and key listings coming back from gpg.

    According to the advisory, those functions start with a 1,024-byte buffer and reallocate it when more space is required. The new buffer pointer is used inside the function, but it is assigned back to the context object only at the end. If the function returns early — for example because of a read error — the context can keep a stale pointer to memory that was already freed. When the context is later released, that memory can be freed a second time. The project notes that other allocations in between may mean common double-free checks in memory allocators are not triggered.

    The trigger described in the announcement is an OpenPGP key that contains a crafted, very long user ID. The project says this double-free can be used to exfiltrate data from applications, and that exploiting it for remote code execution cannot be ruled out. It does not report whether attacks have been observed, and this article does not add that claim.

    Who is affected

    The advisory says all software using a GPGME version prior to 2.3.0 — as a shared library, DLL, or statically linked binary — is affected. Examples it gives include:

    • Gpg4win
    • GnuPG Desktop
    • GnuPG VS-Desktop
    • Most mail clients
    • Many XMPP clients
    • Samba
    • Flatpack, which is the spelling used in the announcement

    The list is illustrative, not exhaustive. Any other program that links GPGME on the same terms is in the same class. The announcement also says there is no need to update GPGMEPP or GPGMEQT for this fix.

    How to update

    The project’s recommended fix is to update the GPGME shared library to version 2.3.1. Windows users who need a DLL can take it from the updated Gpg4win package; the announcement says Gpg4win 5.1.2, which includes the fixed library, the Kleopatra GUI, and a PDF reader, has been released at gpg4win.org. New GnuPG Desktop and GnuPG VS-Desktop versions that use the fixed library were also released.

    If a program statically links GPGME, the advisory says it must be rebuilt against GPGME 2.3.1. If the library cannot be updated for some reason, the announcement includes a patch that the project says likely applies cleanly even to very old versions. Source and a signature are published at the project’s usual download locations, including gpgme-2.3.1.tar.bz2. The announcement also points to Debian-style packages at repos.gnupg.org and to the project’s integrity-check instructions. Verify downloads against those official instructions rather than a checksum copied from a third-party article.

    Compared with GPGME 2.2.0, version 2.3.1 also adds algorithm-mapping constants — GPGME_PK_MLKEM, GPGME_PK_MLDSA, and GPGME_PK_DLTHM — alongside the security fix. Those additions are listed in the announcement’s noteworthy-changes section; they are not a substitute for installing the double-free patch.

    Disclosure timeline

    The vulnerability was discovered by Johan Carlsson. The project says GitLab informed it on November 12, 2026, and that a coordinated disclosure had been set for November 25. Because of what the announcement calls the new Ruby2Shell bug, GitLab had to update earlier, and GnuPG also disclosed the GPGME bug on November 20, 2026. The noteworthy-changes block dates the 2.3.1 release to November 19, 2026. This article does not expand the Ruby2Shell reference beyond that official explanation for the earlier date.

    How this differs from other recent security updates

    This is a library update in the GnuPG stack, not a web-server, hypervisor, or language-runtime patch. Recent coverage on this site has included the November 2026 PHP security releases, F5’s out-of-band BIG-IP notification, and VMware VMSA-2026-0009. Those advisories cover different products and should be handled on their own patch tracks. GPGME 2.3.1 is specifically for applications and installers that bundle or link this library.

    Key facts

    ItemWhat official sources say
    AdvisoryGnuPG security advisory for GPGME, posted to gnupg-announce on November 20, 2026, by Werner Koch.
    IdentifierCVE-2026-129975; project tracker T8557.
    FlawA double-free in functions that read GnuPG status lines and key listings, triggerable by an OpenPGP key with a crafted, very long user ID.
    Impact statedData exfiltration from affected applications is possible, for example via signed data. Remote code execution cannot be ruled out. Immediate update is strongly suggested.
    Affected versionsAll software using GPGME prior to 2.3.0, including shared libraries, DLLs, and statically linked binaries. Version 2.3.0 was never publicly available. The fixed public release is 2.3.1 (November 19, 2026).
    Examples namedGpg4win, GnuPG Desktop, GnuPG VS-Desktop, most mail clients, many XMPP clients, Samba, and Flatpack, as spelled in the advisory.
    FixesUpdate the shared library to 2.3.1; rebuild statically linked programs against 2.3.1; or apply the project’s attached patch. Gpg4win 5.1.2 includes the fixed library. GPGMEPP and GPGMEQT do not need an update for this bug.
    Credit and timingDiscovered by Johan Carlsson; reported via GitLab on November 12, 2026; disclosed November 20 after a planned November 25 date was moved up.

    FAQ

    What is CVE-2026-129975?

    It is a critical double-free in GPGME, the library programs use to work with GnuPG. The official advisory says an OpenPGP key with a crafted, very long user ID can trigger it in the code that reads status lines and key listings from GnuPG.

    Which GPGME version fixes the bug?

    GPGME 2.3.1, dated November 19, 2026, in the announcement’s noteworthy-changes list. The advisory says version 2.3.0 was never publicly available, so 2.3.1 is the fixed public release.

    Does this affect only GnuPG’s own apps?

    No. The advisory says all software using a GPGME version prior to 2.3.0 is affected, whether the library is shared, a Windows DLL, or statically linked. Besides Gpg4win and the GnuPG desktop packages, it names most mail clients, many XMPP clients, Samba, and Flatpack as examples.

    Can this bug be used for remote code execution?

    The project says a remote code execution attack cannot be ruled out. It also says the double-free can be used to exfiltrate data from applications, for example by sending signed data. It strongly suggests updating immediately. This article does not add exploit details.

    What should Windows users install?

    The announcement points Windows users who need a DLL to the updated Gpg4win package and says Gpg4win 5.1.2 includes the fixed GPGME library, Kleopatra, and a PDF reader. Download it from the official Gpg4win site and follow GnuPG’s integrity-check guidance.

    What if our software statically links GPGME?

    The advisory says statically linked binaries need to be rebuilt against GPGME 2.3.1. If the library cannot be updated, the announcement includes a patch that the project says likely applies even to very old versions.

    Do GPGMEPP or GPGMEQT need a separate update?

    The announcement says there is no need to update GPGMEPP or GPGMEQT for this fix. The required change is in GPGME itself.

    Why was the bug disclosed before November 25?

    GnuPG says GitLab informed it on November 12 and that coordinated disclosure had been set for November 25. Because of a new Ruby2Shell bug, GitLab had to update earlier, and GnuPG disclosed the GPGME issue on November 20, 2026.