→ Back to Home
Application Security

Critical Flaw in GPGME Library Exposes Applications to Remote Code Execution via Malicious OpenPGP Keys

A critical vulnerability, CVE-2026-129975, has been identified in GnuPG Made Easy (GPGME), the C library widely used by applications to interface with GnuPG for OpenPGP operations. The flaw is a double-free error that can be triggered by a maliciously constructed OpenPGP key containing an exceptionally long user ID. GnuPG, the maintainer, has acknowledged this as a "critical security bug found in all prior versions" and has released GPGME 2.3.1 to address it. This vulnerability is significant for any organization or developer whose applications rely on GPGME for handling OpenPGP keys. The ability to trigger a double-free error with a specially crafted input opens the door to severe security consequences, including data exfiltration from applications and, potentially, remote code execution. The fact that GnuPG itself cannot rule out remote code execution underscores the severity. While no active exploitation has been reported, the widespread use of GPGME means a large attack surface for this kind of vulnerability. This incident fits into a broader trend in application security where vulnerabilities in foundational libraries and components can have far-reaching impacts across the software supply chain. Similar to past critical flaws in widely used components, the GPGME vulnerability demonstrates that even well-established cryptographic libraries are not immune to serious defects. The challenge is compounded by the fact that many applications integrate these libraries, making rapid patching across an entire ecosystem difficult. The increasing complexity of software dependencies means that a single vulnerability in a core component can ripple through countless applications, affecting various industries and users. Practitioners should prioritize updating their GPGME installations to version 2.3.1 immediately. For Windows users, Gpg4win 5.1.2 includes the fix. It's crucial to check package changelogs for specific distributions to confirm the patch for T8557 or CVE-2026-129975. Given the potential for remote code execution, organizations should also review their threat models for applications handling OpenPGP keys and consider implementing additional layers of defense, such as input validation and sandboxing, where feasible. This serves as a stark reminder that robust application security requires continuous vigilance over all dependencies, not just proprietary code.
#gpgme#openpgp#vulnerability#double free#remote code execution#cryptography
Read original source