GnuPG Warns Critical GPGME Flaw Could Expose App Data via Malicious OpenPGP Keys
AI-summarised brief · reviewed before publication
The GnuPG project disclosed a critical memory‑corruption flaw (CVE‑2026‑129975) in GPGME, the library used by countless applications to interface with GnuPG. A specially crafted OpenPGP key with an excessively long user ID can trigger a double‑free bug in the read_status() and read_colon_line() routines, potentially allowing an attacker to steal data and possibly achieve remote code execution. The vulnerability affects all software that links to GPGME versions prior to 2.3.0, including major mail and XMPP clients, Samba, and GnuPG’s own Windows packages such as Gpg4win and GnuPG Desktop. No exploits have been reported. The project released GPGME 2.3.1 this week as a fix; earlier versions lack an interim workaround. Developers are urged to update immediately to prevent potential data breaches in environments.
💡 Why It Matters
- · Attackers can weaponize ordinary key imports to siphon confidential information, turning a routine cryptographic operation into a data‑leak vector.