知Yizhi Daily
← Back to this edition

AI

GPGME Fixes Double-Free Vulnerability That Could Lead to Data Theft

Edition 2026-11-22 · 08:00 Beijing time

The GnuPG team released GPGME 2.3.1, fixing the critical double-free vulnerability CVE-2026-129975 in all older versions. An attacker could use an OpenPGP key containing an overly long user ID to trigger the flaw in scenarios such as sending signed data and steal application data; remote code execution cannot be ruled out. Affected areas include email and XMPP clients as well as Samba.

The advisory was issued by Werner Koch on November 20, 2026. The vulnerability stems from two internal GPGME functions that read gpg status lines and key lists: the program initially allocates a 1024-byte buffer and reallocates when space is insufficient; if a function returns early because of a read error or another event, the context object still retains a pointer to the freed old buffer, ultimately causing a second free when the context is released.

An attacker can trigger the double free through an OpenPGP key containing a specially crafted overly long user ID. The advisory says the flaw can be used to steal data from applications, for example by sending signed data; whether it can be further exploited for remote code execution cannot be ruled out, so immediate updating is strongly recommended.

The vulnerability was discovered by Johan Carlsson, and GitLab notified the GnuPG team on November 12. The two sides initially planned coordinated disclosure for November 25, but because of the newly emerged Ruby2Shell flaw, GitLab needed to update earlier, and the GPGME vulnerability was consequently disclosed on November 20.

All software using GPGME before 2.3.0 as a shared library, DLL, or static link is affected. The advisory lists Gpg4win, GnuPG Desktop, GnuPG VS-Desktop, most email clients, many XMPP clients, Samba, and Flatpak. The solution is to update to GPGME 2.3.1; statically linked binaries need to be rebuilt against that version. GPGMEPP and GPGMEQT do not need updates.

Original sources

Hacker News ↗
Back to this editionOpen interactive reader