GnuPG vulnerabilities in 2026: GPGME CVE-2026-129975 (not a breach)
GnuPG is the free OpenPGP implementation behind encrypted email, signed software releases and many Linux package managers, and GPGME is the library most applications use to call it. This page tracks serious GnuPG and GPGME vulnerabilities we have covered and keeps them apart from any claim of a breach of the project.
Short answer
Was GnuPG hacked?
No breach of the GnuPG project is reported in the sources we read; CVE-2026-129975 is a vulnerability in GPGME, not a breach of GnuPG. GnuPG's 20 November 2026 advisory says a crafted OpenPGP key with a very long user ID can trigger a double free in every GPGME release before 2.3.0, whether used as a shared library, DLL or statically linked.
GnuPG calls it critical, says it can be used to exfiltrate data from applications and that remote code execution "can't be ruled out". It is fixed in GPGME 2.3.1 and legacy 1.24.4, and Gpg4win 5.1.2 includes the fix. No exploitation has been reported.
Timeline at a glance
12 Nov 2026GitLab reports the GPGME double free (found by Johan Carlsson) to GnuPG. (GnuPG)Not a breach
20 Nov 2026GnuPG advisory for CVE-2026-129975; GPGME 2.3.1 and 1.24.4 released; Gpg4win 5.1.2 fixed. No exploitation reported. (GnuPG)Not a breach
Last updated 22 November 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.
GnuPG incident timeline, in detail
Confirmed = acknowledged by GnuPG, a regulator filing or a court. Reported = credible reporting GnuPG has not fully confirmed. Unverified claim = an attacker or leak-site claim.
Nov 2026Not a breachProduct vulnerability (memory corruption)
CVE-2026-129975: double free in GPGME from a crafted OpenPGP key
What happened. Two GPGME functions that read gpg status lines and key listings start with a 1024-byte buffer and reallocate it; on an early return such as a read error the new pointer is not saved, so the memory is freed twice. A crafted key with a very long user ID triggers it. All versions before 2.3.0 are affected; GnuPG names Gpg4win, GnuPG Desktop and VS-Desktop, most mail clients, many XMPP clients, Samba and Flatpak as users. Fixed in GPGME 2.3.1 (2.3.0 was never publicly released) and 1.24.4; statically linked programs must be rebuilt; GPGMEPP and QGpgME need no update.
Impact. GnuPG says the bug can be used to exfiltrate data from applications, for example by sending signed data, and that RCE cannot be ruled out. No exploitation is reported. A patch for older versions is attached to the advisory. Disclosure moved from 25 to 20 November because GitLab had to update earlier for Ruby2Shell.
Fixed versions: the advisory names GPGME 2.3.1 only; the 1.24.4 fix appears in that release's NEWS file and on gnupg.org, with a warning that the legacy branch may not get every security patch.
Severity: GnuPG calls it critical; there was no CVSS score or CVE.org record when we checked on 22 November 2026.
The pattern across the record
Libraries spread a bug into many products
One flaw in GPGME reaches mail clients, chat clients, Samba and Flatpak, and statically linked copies stay vulnerable until each vendor rebuilds.
Vulnerabilities are not breaches
Nothing reported shows an intrusion at the GnuPG project. The exposure is to systems running unpatched GPGME.
What it means for GnuPG customers — and what to do
If you use encrypted email, Gpg4win or Linux systems with GnuPG, the question is which copies of GPGME you run and whether any are statically linked.
1.Update GPGME and Gpg4win
Move to GPGME 2.3.1 (or 1.24.4 as a stopgap) and Gpg4win 5.1.2, or your distribution's patched package.
Independent analysis for security-leadership education; not affiliated with or endorsed by GnuPG. Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.