AEGLIX News
The GnuPG project has warned that a critical memory bug in GPGME can be triggered by a malicious OpenPGP key containing an unusually long user ID, potentially allowing theft of data from affected applications, according to an advisory released this week. The flaw is tracked as CVE-2026-129975 and affects all software using GPGME before version 2.3.0, including shared libraries, Windows DLLs, and statically linked copies. The project has not reported any attacks exploiting the flaw, though remote code execution cannot be ruled out.
The vulnerability impacts a broad ecosystem of software that relies on GPGME for OpenPGP operations. Examples include most mail clients, many XMPP clients, Samba, Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop packages. Because bundled and statically linked copies are affected, updates to the system's shared library do not reach them, requiring separate action by each application vendor or user. GPGMEPP and GPGMEQT do not need an update, the project noted.
The bug is a double free located in the read_status() and read_colon_line() routines that read status lines and key listings from GnuPG. A malicious key with an unusually long user ID can trigger this condition when processed by vulnerable versions, leading to memory corruption that could be exploited to steal application data. The project emphasized that while no exploitation has been reported, the potential for remote code execution cannot be excluded given the nature of the memory error.
The fixed library version is GPGME 2.3.1, released this week; version 2.3.0 was never publicly available. Windows users should update to Gpg4win 5.1.2, which bundles the fixed library. Older versions that cannot move to 2.3.1 can use a patch from the advisory or the legacy branch fixed release 1.24.4. GPGMEPP and GPGMEQT do not require an update.
Report prepared 2026-11-21 · Based on reporting from The Hacker News. Source publication date above; subsequent developments may not be reflected.