Security

GnuPG Releases GPGME 2.3.1 and Gpg4win 5.1.2 to Fix a Critical Library Flaw

Leave a comment

The GnuPG project has released GPGME 2.3.1 to fix a critical flaw in GPGME, the library many programs use to work with GnuPG, The Hacker News reports. The issue is tracked as CVE-2026-129975. The project’s announcement says software using GPGME before 2.3.0 is affected, whether the library is loaded as a shared library, a Windows DLL, or statically linked, and it lists examples such as most mail clients, many XMPP clients, Samba, and its own Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop packages. A 2.3.0 release was never made public. The project has not reported attacks exploiting the flaw.

What to install depends on how the library is shipped. Shared-library users should move to GPGME 2.3.1. On Windows, Gpg4win 5.1.2 bundles the fixed library, and the Gpg4win changelog calls the issue severe and says to update as soon as possible. There is also a fixed legacy release, 1.24.4, for older branches that cannot move to 2.3.1. Statically linked or bundled copies are not fixed by a system-library update; those applications need their own rebuilt releases. The project says GPGMEPP and GPGMEQT do not need an update, and it offers no interim workaround if you cannot update yet. I am not going to walk through the vulnerability here. Get the fixed builds from the project and confirm the version you are actually running.

My take

A library this widely embedded is the wrong place to linger on a critical fix, especially if a mail client or another app shipped its own copy. Update GPGME or Gpg4win, and check whether any bundled app still needs its own rebuild.

God Bless, and Use the Source!

References & Further Reading

Subscribe (RSS) Follow Security via RSS

Leave a note

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.