GnuPG announces GPGME 2.3.1 to fix a critical flaw, tracked as T8557 and CVE-2026-129975. A specially crafted OpenPGP key with an extremely long user ID can trigger a double free while GPGME reads status lines or key listings from GnuPG. The underlying bug occurs when a growing buffer is reallocated but its updated pointer is not saved in the context until the function finishes. If an error or other event causes an early return, the context retains a pointer to freed memory and may free it again later. The flaw can be used to exfiltrate data - for example, through signed content - and remote code execution cannot be ruled out.
Software using GPGME versions before 2.3.1 is affected, whether the library is shared, provided as a DLL, or statically linked; the advisory notes that version 2.3.0 was never publicly released. Potentially affected products include Gpg4win, GnuPG Desktop, mail and XMPP clients, Samba, and Flatpak. Users should update the library to 2.3.1, or rebuild statically linked programs against that release; an attached patch is offered for installations that cannot upgrade. Updated Gpg4win, GnuPG Desktop, and VS-Desktop releases are also available. No update to GPGMEPP or GPGMEQT is needed. The release additionally adds constants and mappings for several cryptographic algorithms.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.