GnuPG Warns Critical GPGME Flaw Could Expose App Data via Malicious OpenPGP Keys
A malicious OpenPGP key with an unusually long user ID can trigger a critical memory bug in GPGME, the standard library that programs use to work with GnuPG. The GnuPG project warned yesterday that the flaw could be used to steal data from affected applications and has released fixed versions. The bug, tracked as CVE-2026-129975, affects all software that uses GPGME before version 2.3.0,
The GnuPG organization has issued a warning regarding a critical flaw in GPGME, a standard library that many programs utilize to interact with GnuPG. The issue, identified as CVE-2026-129975, arises from a malicious OpenPGP key featuring an abnormally lengthy user ID. According to the group, this vulnerability could enable attackers to extract data from affected applications. Consequently, GnuPG has released updated versions to rectify the flaw.
The vulnerability, which applies to any software employing GPGME prior to version 2.3.0, encompasses various types of installations such as shared libraries, Windows DLLs, and statically linked programs. Examples provided by the project include popular email clients, several XMPP clients, Samba, as well as GnuPG's own offerings like Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop.
The organization has not yet reported any actual attacks exploiting this flaw, but cautions that remote code execution cannot be entirely ruled out.
The flaw, categorized as a double free, occurs in two functions, read_status() and read_colon_line(), which process status lines and key listings originating from GnuPG. When the input becomes excessively long, these functions allocate a larger buffer to store the data. However, if an error arises during this process, the routine fails to update the new memory address, thereby retaining a pointer to memory that has already been previously freed.
This subsequently triggers a second free operation, as explained in the project's tracker entry. The flaw discovery credited to Johan Carlsson and reported to GnuPG by GitLab last week. Disclosure was accelerated to November 25 due to the simultaneous handling of another critical issue, the Ruby2Shell bug, which necessitated earlier updates.
The corrected library version is now GPGME 2.3.1, released this week. A version 2.3.0 was never made publicly accessible. For software that cannot be updated immediately, there are currently no interim solutions recommended by the organization.
Rewritten by urgent.news; may contain errors — check the original.