Technology
GnuPG patches critical GPGME flaw with possible remote code execution risk
Hacker News reports GnuPG released GPGME 2.3.1 to fix a double-free flaw triggered by a crafted OpenPGP key.
The short version
- Hacker News reports that GnuPG released GPGME 2.3.1 to fix a critical security bug present in all prior versions.[Hacker News]
- The flaw is a double free triggered by an OpenPGP key with a crafted, very long user ID, which GnuPG says could be used to exfiltrate data.[Hacker News]
- GnuPG says remote code execution cannot be ruled out, and disclosure moved from November 25 to November 20 after a separate GitLab bug.[Hacker News]
Key facts
- GnuPG announced GPGME 2.3.1 to fix a critical security bug found in all prior versions.[Hacker News]
- The vulnerability is tracked as CVE-2026-129975 and internal ID T8557.[Hacker News]
- The bug is a double free triggered by an OpenPGP key containing a crafted, very long user ID.[Hacker News]
- Johan Carlsson discovered the vulnerability, and GitLab informed GnuPG about it on November 12, 2026.[Hacker News]
- Disclosure moved from a planned November 25, 2026 date to November 20, 2026, because GitLab had to update earlier due to a Ruby2Shell bug.[Hacker News]
What remains uncertain
- GnuPG says remote code execution cannot be ruled out, but it has not confirmed that the bug can be exploited that way.[Hacker News]
- Only Hacker News reports this event, so the details rest on a single outlet's account of the GnuPG advisory.[Hacker News]
Sources
Outlet counts describe coverage, not independent confirmation. Reports may share a wire service or original source.
- RCE in GnupgHacker News