Security
GnuPG fixes a critical GPGME double-free flaw that a booby-trapped OpenPGP key can trigger; version 2.3.1 is the fix
GPGME 2.3.1 fixes a critical double free (CVE-2026-129975) that a crafted OpenPGP key with a very long user ID can trigger.
The GnuPG project released GPGME 2.3.1 to fix CVE-2026-129975, a critical double-free bug that a crafted OpenPGP key with an unusually long user ID can trigger. GPGME is the library applications use to call GnuPG, so the advisory of 20 November affects every program that links it.
The essentials
- The bug: GPGME reallocates a status buffer and then frees it twice when it reads a key with a very long user ID. The advisory says it can be used to exfiltrate data from applications, and it does not rule out remote code execution, per Lavx.
- How it is triggered: an attacker sends a signed message, a key or a key update to an application that uses GPGME. It affects releases before 2.3.1, and Ostorlab adds that the 1.x line is fixed in 1.24.4.
- Who is exposed: mail clients, XMPP clients, Flatpak and Samba are among the software named by Hardware Busters. The bug had been in the library for about 24 years, it reports.
- What to update: GPGME 2.3.1 for the shared library or DLL. On Windows, Gpg4win 5.1.2 bundles the fixed library, and statically linked programs need a rebuild with the fixed version.
Credit and timing
Johan Carlsson discovered the flaw and GitLab reported it to GnuPG, according to Mallory. Werner Koch signed the advisory, which Runtime Wire says was disclosed five days earlier than planned.
What is not established
- Whether the flaw is being exploited in the wild: not stated in the sources.
- A confirmed remote code execution exploit: not stated in the sources.
- The exact list of affected applications: not stated in the sources.
Summary table
| Point | What is stated as of November 21, 2026 | Source |
|---|---|---|
| Advisory date | 20 November 2026 | Runtime Wire |
| Fixed version | GPGME 2.3.1 | The Hacker News |
| Windows bundle | Gpg4win 5.1.2 | InfosecToday |
FAQ
How do I fix the GPGME flaw?
Update to GPGME 2.3.1 (or Gpg4win 5.1.2 on Windows), and rebuild statically linked programs against the fixed library.
Sources
- The Hacker News: GnuPG Warns Critical GPGME Flaw Could Expose App Data via Malicious OpenPGP Keys (verified 2026-11-21)
- Lavx: GnuPG releases GPGME 2.3.1 to fix critical double-free vulnerability (verified 2026-11-21)
- Hardware Busters: GPGME Double Free Bug Hid in GnuPG’s Glue Library for 24 Years (verified 2026-11-21)
- Ostorlab: GPGME Double Free: Data Theft, Possible RCE (CVE-2026-129975) (verified 2026-11-21)
- Runtime Wire: GnuPG urges immediate GPGME update over double-free flaw in malicious OpenPGP keys (verified 2026-11-21)
- InfosecToday: GnuPG Warns Critical GPGME Flaw Could Expose App Data via Malicious OpenPGP Keys (verified 2026-11-21)
- Mallory: Critical GPGME Double-Free Flaw Could Expose Application Data via Malicious OpenPGP Keys (verified 2026-11-21)
Spotted an error in this article? Report it · Our corrections policy