CVE-2026-129975: Double-free in GPGME OpenPGP key processing
CVE-2026-129975 is a critical double-free vulnerability in GPGME, a library used by applications to interact with GnuPG. Processing an OpenPGP key with a crafted, very long user ID can trigger faulty buffer management in the read_status() and read_colon_line() routines, which process GnuPG status output and key listings. These routines reallocate a buffer but defer updating the owning context's pointer until successful completion. An intervening error can leave the context referencing freed memory, which is freed again during cleanup. Intervening allocations can prevent common allocator double-free checks from detecting the condition. Exploitation can disclose application data or cause denial of service; arbitrary code execution is considered possible but has not been demonstrated. Unpatched GPGME releases before 2.3.0 are affected across shared-library, Windows DLL, bundled, and statically linked deployments. Version 2.3.0 was not publicly released; 2.3.1 is the fixed current release.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Processing malicious OpenPGP key material can expose data held by the affected application or crash it. Potential arbitrary code execution could compromise the application within its execution privileges, although remote code execution has not been demonstrated. Exposure extends to applications incorporating vulnerable GPGME copies, including mail clients, XMPP clients, Samba, and GnuPG desktop distributions. No active exploitation or publicly available exploits were reported at disclosure.
Mitigation
If you can’t patch tonight, do this now.
No validated interim workaround has been identified. Updating or applying the upstream patch is the established corrective action.
Remediation
Patch, then assume compromise.
Upgrade to GPGME 2.3.1 or a vendor package containing the fix. GPGME 1.24.4 provides a fixed legacy-branch release. For Debian stable (trixie), upgrade the gpgme1.0 packages to 1.24.2-3+deb13u1 or later fixed versions. Windows users can obtain the corrected library through Gpg4win 5.1.2; updated GnuPG Desktop and GnuPG VS-Desktop releases were also announced. Rebuild statically linked applications against a fixed GPGME version and update applications that bundle their own copy; updating the system library alone does not fix these deployments. If upgrading is not possible, apply the upstream security patch or an equivalent vendor backport. GPGMEPP and GPGMEQT do not independently require updates for this issue.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-129975 exploited in the wild?
- As of Nov 21, 2026, Mallory has no reports of CVE-2026-129975 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-129975?
- As of Nov 21, 2026, Mallory has found no public exploit for CVE-2026-129975.
- Is there a patch for CVE-2026-129975?
- Upgrade to GPGME 2.3.1 or a vendor package containing the fix. GPGME 1.24.4 provides a fixed legacy-branch release.
Recent activity
51 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.