Skip to content
Security & Trust

A flaw in GPGME, the library behind many email clients, needs a patch

A crafted OpenPGP key can corrupt memory in software that most teams never chose directly. Version 2.3.1 fixes it.

W
WebPulse Newsroom
AI-assisted · 4 min read
Share on X LinkedIn
A flaw in GPGME, the library behind many email clients, needs a patch

Graphic: WebPulse, drawn from the sourced facts in this story.

In brief
  • The GnuPG project announced GPGME 2.3.1 on November 20, 2026, fixing CVE-2026-129975, a memory flaw triggered by a crafted OpenPGP key.
  • The flaw sits in a shared library inside many products, so many organisations may carry it without having chosen it.
  • Inventory which products and vendors use GPGME, update to 2.3.1, and rebuild any statically linked software.

The risk sits in a part nobody bought

Many organisations track the products they buy more closely than the libraries inside them. A flaw in one of those libraries reaches every product that carries it, and no one decided to take that risk.

That is the lesson of CVE-2026-129975, a memory flaw in GPGME. GPGME is the library that lets applications talk to GnuPG, the widely used OpenPGP encryption tool. The GnuPG project announced the fix on November 20, 2026, in GPGME version 2.3.1. The release notes date the version itself November 19.

What the GnuPG project says happened

The project describes the bug as serious and says every earlier version has it. According to its announcement, an OpenPGP key with a crafted, very long user ID can trigger a double free. That means the program releases the same piece of memory twice.

The announcement says the double free can be used to exfiltrate data from applications, for example by sending signed data. It adds that using the bug for remote code execution cannot be ruled out. The project therefore suggests an immediate update.

The announcement does not say whether anyone has exploited the flaw.

How the bug works

GPGME reads output from the gpg program. Two internal functions read status lines and key listings. Each starts with a 1,024-byte buffer and grows it when the data does not fit.

The fault is in the bookkeeping. When a buffer grows, the function uses the new location. But it only records that location in the shared context object at the end. If the function exits early, for example after a read error, the context still points to the old, freed memory.

When the context is later cleaned up, that memory is freed a second time. The announcement notes that other memory allocations in between can stop the usual double-free checks in memory allocators from catching it.

The pattern is easy to picture. Someone moves house and leaves a forwarding note at the old address. The note is only filed once the move is complete. If the move is interrupted, the old address is still on file, and the same property gets handed over twice.

Who carries the exposure

The project says all software using a GPGME version before 2.3.0 is affected. Version 2.3.0 was never publicly released, so 2.3.1 is the first fixed version. The flaw covers the shared library, a Windows DLL, or a statically linked copy.

Its examples span the project's own Windows and desktop products, Gpg4win, GnuPG Desktop and GnuPG VS-Desktop. They also reach well beyond: the project names Samba and Flatpak, and says that most mail clients and many XMPP chat clients rely on GPGME too.

The trigger is a malicious key. Software that handles keys from outside parties, such as mail clients, is the natural place to look. The announcement does not rank which products face the most exposure.

The announcement also gives a timeline. The project says GitLab informed it on November 12, 2026, and that the flaw was found by Johan Carlsson. A coordinated disclosure was first set for November 25. The project says it disclosed on November 20 instead, because GitLab had to update early over a separate bug it calls Ruby2Shell.

What to do and ask

The fix is GPGME 2.3.1. Windows users can take the DLL from the updated Gpg4win, version 5.1.2. Linux users should update the shared library through their usual package channel. The project also provides Debian-style packages.

Statically linked programs need a rebuild against 2.3.1. Updating the system library does not change them. The project also attached a patch it says likely applies cleanly even to very old versions. It says GPGMEPP and GPGMEQT need no update.

Leaders can put four questions to their teams:

Which of our products and internal tools use GPGME, and in what form: shared library, DLL or static copy? Which of our vendors ship it inside their own software? Which of our systems accept OpenPGP keys from outside parties? Who owns the rebuild for anything linked statically?

A library that few people have heard of sits under a great deal of everyday software. The inventory of what is inside your products is the control that makes a patch like this quick to apply.

Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: lists.gnupg.org.

CVE-2026-129975: GPGME memory flaw