CVE-2026-129975: scope and immediate risk
The GnuPG project warned that CVE-2026-129975 is a critical flaw in GPGME that "could be used to steal data from affected applications" and has released fixed versions. The project has not reported any attacks exploiting the flaw, and it notes that remote code execution cannot be ruled out. The advisory shows a conceivable path to exploitation: signed data sent to an application can carry a malicious OpenPGP key with an unusually long user ID that triggers the bug. The advisory does not list which programs pass such material to the library without a manual key import.
Technical cause: double free in read_status() and read_colon_line()
The defect is a double free. It appears in two routines — read_status() and read_colon_line() — that parse status lines and key listings returned from GnuPG. When input exceeds a buffer's size, the routines attempt to reallocate to a larger buffer but only update the recorded address if the operation completes without error. An intermediate error can leave a pointer to memory that was already freed; later cleanup then releases the same memory a second time, producing the double free the project's tracker entry describes.

This site is the portfolio.
OSINTSights runs on Cloudflare Workers, D1, R2, and Vectorize, with an AI pipeline on Hetzner ARM. Nubivance designed, built, and operates it. We do the same for clients.
See what we buildSoftware and deployments affected
The bug affects all software that uses GPGME before version 2.3.0, whether the library is loaded as a shared library, a Windows DLL, or statically linked into the program. The GnuPG project cites examples including most mail clients, many XMPP clients, Samba, and its own Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop packages. Statically linked or bundled copies of GPGME are affected independently of a system update to the shared library; those applications need their own rebuilt releases.
Remediation: GPGME 2.3.1, Gpg4win 5.1.2, legacy 1.24.4 and patches
The fixed library is GPGME 2.3.1, released this week. The advisory notes that a version 2.3.0 was never publicly available. For shared libraries and DLLs, the project directs users to update to GPGME 2.3.1 via the project's official downloads and security advisory. Windows users should install Gpg4win 5.1.2, which bundles the fixed library; its release notes call the issue "severe" and advise updating as soon as possible.
For older releases that cannot move to 2.3.1, the advisory carries a patch, and the legacy branch has its own fixed release, 1.24.4; the legacy release notes say the project cannot guarantee that the branch will see every security patch. The advisory also specifies that GPGMEPP and GPGMEQT do not require an update. The advisory offers no interim workaround for software that cannot update yet.
How mail clients, Samba, and Gpg4win should respond
- Mail clients and XMPP clients that hand signed data or key listings to GPGME: verify whether they load GPGME dynamically or bundle it. If they use a shared library, update the system package to GPGME 2.3.1; if they contain a statically linked or bundled copy, require a rebuilt release that includes the fixed library.
- Samba administrators and enterprise packagers: treat packaged or embedded copies as affected even if a system-level shared library is updated, and coordinate with upstreams for rebuilt releases or apply the advisory patch where moving to 2.3.1 is not possible.
- Gpg4win and Windows desktop users: install Gpg4win 5.1.2, which bundles the fixed library. The project's release notes explicitly call the issue severe and recommend prompt updating.
The bug was reported to the project by GitLab last week after being found by Johan Carlsson. Disclosure was set for November 25, the advisory says, and moved up because the new Ruby2Shell bug forced the company to update earlier. The advisory does not provide a mitigation for systems that cannot immediately install the fixed library, and it leaves open which programs will, in practice, pass signed material to GPGME without a manual key import — a detail relevant to assessing exposure in real deployments.
For administrators and users, the clear, immediate task is to inventory software that links to GPGME and to apply GPGME 2.3.1, install Gpg4win 5.1.2, or obtain rebuilt application releases that incorporate the fix. The project's advisory, the tracker entry, and the listed release notes are the single authoritative sources for the available fixes and patches.
https://thehackernews.com/2026/11/gnupg-warns-critical-gpgme-flaw-could.html




