Skip to content
CVE-2026-129975: update GPGME and verify bundled libraries

CVE-2026-129975: update GPGME and verify bundled libraries

November 21, 2026

GnuPG disclosed CVE-2026-129975, also tracked as T8557, on November 20, 2026 and classified it as Critical. Update applications using earlier released upstream GPGME versions to a build containing GPGME 2.3.1, or install a distribution package explicitly confirmed to fix this CVE. The vendor recommends an immediate update. GnuPG security news

Choose the package that supplies GPGME

GPGME is the library through which applications use GnuPG. The upstream download page dates GPGME 2.3.1 to November 19. Application vendors may bundle the library or link it statically; updating a system package alone does not replace those copies. Statically linked applications need a rebuild against the corrected library.

InstallationPatch action
Upstream GPGMEInstall 2.3.1 and update dependent applications.
Distribution packageInstall the package revision identified by that distribution for CVE-2026-129975. Backports can retain an older upstream version.
Bundled or statically linked libraryObtain a corrected application build from its supplier, or rebuild the application against 2.3.1.
Gpg4win on WindowsInstall the 5.1.2 security update released November 20.

The Gpg4win change history lists GPGME 2.3.1 inside 5.1.2. Its GnuPG engine remains 2.5.24, the same engine version listed for Gpg4win 5.1.1. An unchanged GnuPG version therefore cannot establish whether the GPGME update is installed.

Verify the application after updating

Record the installed application build and its GPGME dependency from package metadata, the supplier’s component inventory, or your build manifest. Check each separately installed application that bundles the library. Keep the vendor’s CVE-to-package mapping with the maintenance record.

Restart affected applications or services after replacement so they load the updated library. For routine acceptance testing, use your own known-good data to confirm normal signing or verification still works. Record the final application and dependency versions; a successful operation alone does not prove the patch is present.

Acknowledgements

This post was created with assistance from AI.

Last updated on