Critical GPGME flaw: how to check whether you should update

Critical GPGME flaw: how to check whether you should update

A malicious OpenPGP key with an unusually long user ID can trigger a critical flaw in GPGME and expose data from affected applications. The GnuPG project released the fix in GPGME 2.3.1; for Windows, Gpg4win 5.1.2 includes the patched library. The flaw, CVE-2026-129975, affects software that incorporates vulnerable versions, whether as a shared library, DLL, or statically linked component.

The list of potentially affected programs includes most email clients, many XMPP clients, Samba, Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop. The specific exposure depends on the version of GPGME each program uses and how it processes OpenPGP material; GnuPG cites signed data sent to an application as an example. It does not identify which programs process such data without a manual key import.

How to tell if you are affected

Start by identifying which programs use OpenPGP on your devices: for example, email clients with encryption features, XMPP tools, or Samba. If you use Gpg4win, GnuPG Desktop, or GnuPG VS-Desktop, check the installed version and look for the corresponding update. Using GnuPG alone is not enough to confirm the risk: the vulnerable component is GPGME, which other applications may include separately.

The vulnerability affects GPGME versions earlier than 2.3.0, but version 2.3.0 was never released, according to the GnuPG advisory. In practice, look for a patched version offered by the project, the application vendor, or your distribution; the version number may vary among packages for different systems.

Product or packageStatus or patched version
Project GPGME2.3.1
Gpg4win5.1.2
Legacy GPGME1.24.4
Debian bookwormFixed in 1.18.0-3+deb12u1
Debian trixieFixed in 1.24.2-3+deb13u1
Debian sidFixed in 2.3.1-1

The Debian versions are those listed by its security tracker and do not necessarily match GPGME's main version number. In bookworm, package 1.18.0-3 is listed as vulnerable; in trixie, 1.24.2-3 is vulnerable. Compare your distribution's package with its security advisory instead of assuming that only version 2.3.1 can contain the fix.

What to do now

  1. Inventory the affected applications. Check devices where you use email or XMPP clients with OpenPGP, Samba, or GnuPG desktop products. The list is a guide to finding possible dependencies; it does not by itself prove that every installation uses a vulnerable version.

  2. Update Gpg4win on Windows. Install Gpg4win 5.1.2 or a later version that includes the fix. Its change history identifies the flaw as CVE-2026-129975 and recommends updating as soon as possible. Gpg4win 5.1.2 includes GPGME 2.3.1.

  3. Update the GPGME package if your application uses a shared library or DLL. GnuPG offers GPGME 2.3.1; it also distributes packages for some Debian variants. On Debian, check the security status of your release and install the corresponding patched package, such as those listed in the table.

  4. Update the application, not just the system when GPGME is statically linked or bundled with the program itself. Installing a newer shared library does not replace the embedded copy: the GnuPG advisory says to rebuild those binaries with GPGME 2.3.1. Look for an application version that announces this update.

  5. If you rely on an older branch, check whether you can install GPGME 1.24.4, the patched version of the legacy branch. GnuPG also publishes a patch for older versions. If you cannot update, coordinate its application with whoever maintains the package or application; the advisory does not offer a general temporary mitigation.

  6. Confirm which components need updating. GPGMEPP and GPGMEQT do not require an update for this flaw, according to GnuPG. For other programs, check separately whether the fix arrived through a system update or an update to the product itself.

Mistakes to avoid

Do not assume the system is fixed just because you updated GnuPG or a system library. An application with statically linked GPGME needs a rebuilt version; it may also include its own DLL. Check the product that actually contains the dependency.

Also, do not dismiss the issue because your version number is lower than 2.3.1: distributions can patch packages with different version numbers, as the Debian packages show. Use your distribution's security status and the specific package version, not an isolated comparison with the upstream version.

Finally, do not rely on avoiding manual key imports as a complete solution. GnuPG describes signed data sent to an application as one possible way to trigger the flaw, but it does not provide a list of programs that process this material automatically or a temporary fix. The project's recommendation is to update; it has also not reported any known attacks exploiting the vulnerability.

Sources: The Hacker News, lists.gnupg.org, GnuPG project tracker, Gpg4win, Debian Security Tracker