Menu

One Key, Two Frees: The GPGME Bug That Turned Trust Infrastructure Into Attack Surface
📰

One Key, Two Frees: The GPGME Bug That Turned Trust Infrastructure Into Attack Surface

DEV Community: encryption·Damiano·about 4 hours ago
#IYV4QLQh
#devtoencryption#devto#dev#advisory#library
Long article (1375 words) — no AI summary yet.
Reading 0:00
15s threshold

On November 20, 2026, Werner Koch announced GPGME 2.3.1 on the gnupg-announce mailing list with a sentence no maintainer enjoys writing: the release "fixes a critical security bug found in all prior versions." The bug is CVE-2026-129975, a double free in GPGME, the library that sits between GnuPG and nearly every application that wants to encrypt, sign, or verify something without reimplementing OpenPGP itself.

The trigger is disarmingly simple. According to the advisory, "by using an OpenPGP key containing a crafted very long user id it is possible to trigger a double free." The same advisory says the double free "can be used to exfiltrate data from applications by sending for example signed data," and that exploiting it for remote code execution "can't be ruled out." That last phrase is the vendor's own, and it is doing a lot of work in this story.

Why this library matters more than most

GPGME, the GnuPG Made Easy library, is not an obscure corner of the ecosystem.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.