---
title: Tip: patching the system gpgme package isn't enough for CVE-2026-129975; find apps that bundle or statically link GPGME | ctxsec
url: https://ctxsec.com/items/tip-gpgme-cve-2026-129975-find-statically-linked-and-bundled-gpgme-not-just-the-system-library
description: "GnuPG says static builds must be rebuilt against GPGME 2.3.1, and Windows apps may ship their own DLL. Flatpak runtimes, mail clients and appliances are the usual places it hides."
status: "guide (based on the GnuPG GPGME advisory, Nov 20, 2026)"
published: 2026-11-21
---

> GnuPG says static builds must be rebuilt against GPGME 2.3.1, and Windows apps may ship their own DLL. Flatpak runtimes, mail clients and appliances are the usual places it hides.

[← Tips & Guides](/tips) · [markdown](/items/tip-gpgme-cve-2026-129975-find-statically-linked-and-bundled-gpgme-not-just-the-system-library.md)

guide (based on the GnuPG GPGME advisory, Nov 20, 2026)

2026-11-21 7:49 AM ET

### Tip: patching the system gpgme package isn't enough for CVE-2026-129975; find apps that bundle or statically link GPGME

- Linux: `ldd` or `lsof | grep libgpgme` for dynamic users; `strings <binary> | grep -i 'gpgme'` on suspects for static builds; `flatpak update` for runtimes.
- Windows: search for `libgpgme-*.dll` outside the Gpg4win folder and update Gpg4win to 5.1.2.
- Until patched, treat unsolicited keys and signed mail from unknown senders with extra caution in automated pipelines that import keys.

Sources: [gnupg-announce: GnuPG Security Advisory for GPGME (T8557, CVE-2026-129975), Werner Koch (Nov 20, 2026)](https://lists.gnupg.org/pipermail/gnupg-announce/2026q4/000517.html)
