العربية
🚨 BreakingSonicWall Gen 6 Firewalls Reach End of Security Patches

GPGME Flaw CVE-2026-129975: Malicious OpenPGP Keys Trigger Double Free

فريق السايبر العربياقرأ بالعربية

GnuPG fixed a critical double-free bug in the GPGME library, CVE-2026-129975, that a crafted OpenPGP key with an oversized user ID can trigger to leak app data.

Source image for: GnuPG Warns Critical GPGME Flaw Could Expose App Data via Malicious OpenPGP Keys
Image: The Hacker News

⚡ Why it matters

GPGME sits underneath most email clients, many XMPP clients, Samba and Gpg4win, so the exposure is broad. The project says remote code execution cannot be ruled out.

The GnuPG project has disclosed a critical memory-safety bug in GPGME, the library applications rely on to talk to GnuPG for encryption and signing. Tracked as CVE-2026-129975, it affects every program built on GPGME releases earlier than 2.3.0, whether the library is loaded as a shared object, shipped as a Windows DLL, or compiled statically into the application.

How the bug works

The issue is a double free: the same block of memory gets released twice. It lives in read_status() and read_colon_line(), two routines that parse status output and key listings returned by GnuPG. When a line is long, they move it into a bigger buffer but only save the new pointer after a clean finish. If an error interrupts the process, a stale pointer to freed memory remains and the cleanup code frees it again.

An attacker can reach the flaw with a crafted OpenPGP key carrying an unusually long user ID. The advisory cites signed data delivered to an application as one example path, but it does not list which programs hand such data to GPGME without a manual key import.

Who is affected

According to the project, affected software includes most email clients, many XMPP clients, Samba, and GnuPG's own Gpg4win, GnuPG Desktop and GnuPG VS-Desktop packages. No in-the-wild exploitation has been reported, though GnuPG says remote code execution cannot be excluded.

Researcher Johan Carlsson found the bug and GitLab reported it to the project. Disclosure, originally planned for November 25, was brought forward.

Recommendations

  • Update to GPGME 2.3.1. Version 2.3.0 was never released publicly.
  • On Windows, update to Gpg4win 5.1.2, which ships the fixed library.
  • Systems that cannot move to 2.3.1 can apply the patch included in the advisory or use legacy release 1.24.4, noting that the legacy branch is not guaranteed to receive every security fix.
  • Watch for vendor updates to applications that bundle or statically link GPGME, since a system library upgrade does not cover them.
  • GPGMEPP and GPGMEQT need no update. There is no interim workaround for software that cannot be patched yet.

Source: The Hacker News

🔗 Sources

This article is original reporting by the Security World editorial team based on the sources listed above; direct quotes are kept short and marked with quotation marks. Corrections and feedback: info [at] securitywd.net.

Related stories