GnuPG Warns of Critical Memory Bug in GPGME
A malicious OpenPGP key with an unusually long user ID can trigger the flaw, which affects software using GPGME before version 2.3.0.
Updated on Nov. 21, 2026 in Software

GnuPG warned that a critical memory bug in GPGME can be triggered by a malicious OpenPGP key with an unusually long user ID, tracked as CVE-2026-129975. The project released fixed GPGME versions addressing the flaw, and has not reported any attacks exploiting it.
Why it matters
GPGME is used by most mail clients, many XMPP clients, Samba, and several encryption desktop tools, so the flaw reaches a wide range of software worldwide. Because remote code execution cannot be ruled out, users and administrators of affected programs are being urged to update promptly.
The flaw is a double free in the read_status() and read_colon_line() routines, which occurs when an error interrupts a buffer reallocation and leaves a pointer to already-freed memory. Gpg4win 5.1.2 bundles the fixed library, but the advisory provides no interim workaround for software that cannot yet be updated.
The players
GnuPG
GnuPG is a free implementation of the OpenPGP encryption standard widely used for securing email and files.
GitLab
GitLab is a web-based DevOps platform used by software teams worldwide for code hosting and continuous integration.
The details
The bug was found by Johan Carlsson and reported to the project by GitLab last week. When input runs long, the affected routines move data to a larger buffer but record the new address only if they finish without errors, so an error in between leaves a dangling pointer that cleanup frees a second time.
Timeline
Last week: GitLab reported the flaw to the GnuPG project.
November 20, 2026: GnuPG issued the warning and released fixed versions.
November 25, 2026: Scheduled public disclosure date, moved up due to the Ruby2Shell bug.
The Tech Race
The GPGME flaw sits inside the OpenPGP library layer that mail clients and secure messaging tools build on, so a single defect propagates across many independent products. Its disclosure was accelerated because a separate Ruby2Shell bug forced earlier updates, showing how coordinated security timing is shaped by competing vulnerabilities.
Anyone using a mail client, XMPP chat program, Samba file sharing, or Gpg4win should check whether their software bundles a GPGME version before 2.3.0 and install the update. Software that cannot be updated yet has no interim workaround, so users should watch for vendor patches.
The takeaway
Check the encryption and messaging software on your devices and confirm it has been updated to a GPGME release at or above 2.3.0. Keep software that depends on this library patched, since updates are the only current remedy.
What happens next
The public disclosure of the flaw is scheduled for November 25, 2026, when full technical details are expected to be released.
Further reading
For related coverage of security patches and open-source tools, explore the Software section.
Source note: This article includes information reported by The Hacker News.



