Get DeafLetter
A weekly selection of signals, vulnerabilities and guides. Critical alerts remain optional.
You can unsubscribe at any time. Privacy policy.
The library handling digital signatures on millions of Linux systems hid a double-free reachable via a specially crafted PGP key. On November 20, 2026, the GnuPG project disclosed CVE-2026-129975, a critical vulnerability in GPGME that allows data exfiltration from applications through OpenPGP keys with abnormally long user IDs. Disclosure came five days early — ahead of the planned November 25 date — because the Ruby2Shell bug forced GitLab into an early infrastructure update.
- CVE-2026-129975 is a double-free in GPGME caused by delayed buffer-pointer assignment after realloc()
- The vector is a crafted OpenPGP key with an abnormally long user ID that forces reallocation of the 1024-byte buffer
- Data exfiltration is confirmed; RCE cannot be ruled out per the official advisory
- GPGME 2.3.1 fixes the bug; no workaround exists for systems that cannot be updated
The Mechanism: Delayed Allocation and a Dangling Pointer
The bug lives in GPGME's internal read_status() and read_colon_line() functions. When the library reads status lines and key listings from gpg, it initially allocates a 1024-byte buffer. If content exceeds that size, the function calls realloc() for more space.
The pointer to the new buffer is used internally, but assignment to the GPGME object context occurs only at the end of the function. If a read error occurs during processing, the function returns early. The context retains the pointer to the original buffer — already freed by realloc() — while the new buffer remains referenced only on the local stack. During cleanup, the error handler frees the pointer in the context: the original buffer is deallocated a second time.
An OpenPGP key with a sufficiently long user ID forces the reallocation and can trigger the necessary read error. Per Werner Koch's advisory, "by using an OpenPGP key containing a crafted very long user id it is possible to trigger a double free." The bug requires no user interaction in applications that automatically process keys or signed data.
Timeline: From Discovery to Early Disclosure
Johan Carlsson discovered the vulnerability; GitLab notified the GnuPG project on November 12, 2026. Coordinated disclosure was slated for November 25 but moved to November 20. The official advisory states that "due to the new Ruby2Shell bug GitLab had to update earlier and thus we also disclosed the GPGME bug on 2026-11-20."
Ruby2Shell forced GitLab into an early infrastructure update, pulling the GPGME disclosure forward. No technical connection between the two bugs is documented; the acceleration is purely logistical. The GnuPG project reports no known exploitation at publication. No CVSS score is assigned in available sources.
Update Chain and Statically Linked Copies
The fixing version is GPGME 2.3.1, released November 19, 2026. Version 2.3.0 was never publicly released. All prior versions are affected, including statically linked copies and DLL distributions. Applications using static linking must be recompiled by vendors to receive the fix.
For Windows, Gpg4win 5.1.2 includes the patched GPGME library. A legacy release 1.24.4 backports the patch, though the project explicitly warns this branch carries no guarantee of future support. GPGMEPP and GPGMEQT, the C++ and Qt interfaces, require no independent update.
"By using an OpenPGP key containing a crafted very long user id it is possible to trigger a double free. This double free can be used exfiltrate data from applications by sending for example signed data. Exploiting this bug to mount an Remote Code Execution attack (RCE) can't be ruled out. Thus an immediate update is highly suggested."
— GnuPG Security Advisory, Werner Koch
What to Do Now
System administrators must update GPGME to version 2.3.1 on all Linux and Unix systems. For distributions maintaining the legacy branch, version 1.24.4 contains the backport but without future support guarantees. Windows users must install Gpg4win 5.1.2.
Vendors with static linking must recompile binaries with GPGME 2.3.1. Applications bundling GPGME as a DLL must update the included package. No separate update of GPGMEPP or GPGMEQT is needed.
Organizations should audit workflows that automatically process OpenPGP keys or signed data from external sources: automated mail clients, signing gateways, build systems that verify signatures. These categories are exposed to the documented vector. No workarounds exist in published material.
The Version Skip: Responsible Disclosure Under Pressure
The decision not to publicly release GPGME 2.3.0 and instead ship 2.3.1 directly with the security fix illustrates atypical release management. The GnuPG project folded the correction into a version that never saw public distribution, likely to avoid an intermediate release exposing users to a known bug.
This choice, combined with the Ruby2Shell-forced acceleration, compressed the preparation window for operators. The 2.3.0→2.3.1 version jump is not documented as standard practice; here it prevented automated package repositories from distributing a vulnerable version. The trade-off is reduced transparency in release history.
What Remains Unknown
The official advisory explicitly leaves several points open. The minimum user ID length required to trigger the bug is not quantified. The complete list of applications that pass signed data to GPGME without manual key import is not identified. The number of potentially affected systems or users is not quantified.
No public exploit is documented in available sources. No CVSS score is assigned. It is unclear whether the bug is technically exploitable for RCE or if the advisory maintains that possibility out of methodological caution. The GnuPG project provides no guidance for auditing specific application exposure.
Closing
CVE-2026-129975 is a long-lived vulnerability in a foundational cryptographic codebase. The commit introducing the bug dates to 2002; the fix arrived 24 years later, spanning dozens of releases and revisions. The attack vector — a PGP key with an abnormally long user ID — is technically trivial but effective because it exploits a memory-management pattern typical of pre-standard C.
The specific lesson here lies in the logistic dependency chain: a third-party bug (Ruby2Shell) accelerated disclosure of a second (GPGME), demonstrating how responsible-disclosure timelines are interdependent. For operators, the priority is identifying automatic key- and signed-data-processing flows, not just updating the library.
Sources: GnuPG Security Advisory (lists.gnupg.org, lists.gnu.org); The Hacker News; LavX News
Sources
Get DeafLetter
A weekly selection of signals, vulnerabilities and guides. Critical alerts remain optional.
You can unsubscribe at any time. Privacy policy.