DKDKCISSP
PolicyINCIDENT

GnuPG Warns Critical GPGME Flaw Could Expose App Data via Malicious OpenPGP Keys

GnuPG has disclosed a critical flaw in GPGME that could allow data theft via malicious OpenPGP keys.

DKCISSP News Desk21 Nov 2026, 4:36 pm2 min read
GnuPG Warns Critical GPGME Flaw Could Expose App Data via Malicious OpenPGP Keys
Image courtesy of The Hacker News. Original report

The GnuPG project has issued a warning about a critical vulnerability in GPGME, a library used to interact with GnuPG, which could be exploited through malicious OpenPGP keys to access sensitive application data.

A critical memory bug in GPGME could allow attackers to steal data from applications using the library. The vulnerability, tracked as CVE-2026-129975, affects all software utilizing GPGME prior to version 2.3.0. GnuPG has released fixed versions to address the flaw, which can be triggered by a malicious OpenPGP key featuring an unusually long user ID.

The flaw is categorized as a double free vulnerability, meaning the same memory is improperly released twice. This occurs within the read_status() and read_colon_line() routines, which handle status lines and key listings from GnuPG. If the input exceeds expected length, the routines attempt to allocate a larger buffer but may leave a pointer to memory that has already been freed if an error occurs during the process.

GPGME is a library that provides an interface for applications to work with GnuPG, which is used for encrypting and signing data. It allows software developers to integrate GnuPG’s cryptographic capabilities into their applications without needing to manage the complexities of the underlying encryption processes. When applications use GPGME, they can perform operations like encrypting emails or signing files while relying on GnuPG for the cryptographic functions.

The vulnerability potentially affects a wide range of applications that utilize GPGME, including various mail clients, XMPP clients, Samba, and GnuPG's own tools such as Gpg4win and GnuPG Desktop. As of now, GnuPG has not reported any instances of the vulnerability being actively exploited, but the risk of remote code execution remains a concern.

The flaw was discovered by researcher Johan Carlsson, who reported it to GnuPG via GitLab. The advisory originally slated for disclosure on November 25 was moved up due to the urgency created by a separate Ruby2Shell bug that necessitated an earlier update.

GnuPG has released GPGME version 2.3.1 to patch the vulnerability, while version 2.3.0 was never made publicly available. The advisory did not provide any interim workarounds for software unable to update immediately, leaving organizations at risk until they can implement the fixed version.

Unknowns include whether any organizations have been targeted or exploited due to this vulnerability and what specific applications are most at risk from this bug.

What security teams should do

  • Update to GPGME version 2.3.1 to mitigate the vulnerability.
DKCISSP VIEWOur take, not reported fact

What it meansGnuPG disclosed a critical vulnerability in GPGME that could allow data theft via malicious OpenPGP keys, which affects various applications using the library.

Ask your IT team this weekWhich applications in our environment use GPGME? How quickly can they be updated?Are there any applications that cannot be updated immediately due to compatibility issues?

DecisionThe IT team updates to GPGME version 2.3.1, and security checks that it was completed.

MORE IN POLICY

More cybersecurity reporting

Handling the NIST 800-171 Rev 3 Transition20 Nov 2026, 7:30 pmCISA Urges Immediate Patching of Java4Shell Flaw That Could Allow Remote Code Execution20 Nov 2026, 3:05 pmUK joins in GTA 6 frenzy as game becomes available worldwide19 Nov 2026, 5:56 pmResearchers Detail iPhone Flaw That Let Apps Record Audio Despite Denied Microphone Permission17 Nov 2026, 5:44 pm