Science & Tech · Cybersecurity · 1 hr ago
GnuPG warns of critical GPGME flaw that could expose app data
GnuPG warned of a critical flaw in GPGME, a library that programs use to work with GnuPG.
The flaw affects software using GPGME versions before 2.3.1, including many mail and messaging clients and some GnuPG products.
A malicious OpenPGP key with a very long user ID can trigger the bug, which releases the same memory twice.
The flaw could let attackers steal data from affected apps, and remote code execution cannot be ruled out.
The project has not reported any attacks exploiting it.
GnuPG has released GPGME 2.3.1 and recommends updating; Windows users can get the fixed library in Gpg4win 5.1.2.
Apps with bundled copies need their own updates, because updating a shared system library will not fix them.
A critical flaw in GPGME could expose data handled by affected applications, the GnuPG project warned.
The flaw is triggered by a malicious OpenPGP key with an unusually long user ID and is tracked as CVE-2026-129975.
It affects software using GPGME versions before 2.3.0, including many mail and XMPP clients and several GnuPG products.
GnuPG released fixed versions, including GPGME 2.3.1 and the legacy release 1.24.4.
The project has not reported attacks exploiting the flaw, but says remote code execution cannot be ruled out.
- Who
- The GnuPG project warned users of software that uses GPGME.
- What
- A critical double-free flaw could expose application data. Remote code execution cannot be ruled out.
- When
- The warning was published on November 21, 2026; the project said the fixed GPGME 2.3.1 was released that week.
- Where
- In GPGME, the library used by programs to work with GnuPG.
- Why
- A malicious OpenPGP key with an unusually long user ID can trigger the memory bug.
This story does not have two clearly opposing sides.
Johan Carlsson reported the flaw to the GnuPG project through GitLab.
The project released fixed GPGME version 2.3.1.
The Hacker News published its report on the warning and flaw.
The advisory's planned disclosure date was moved earlier, the article said.
- CVE
- CVE-2026-129975
- Affected versions
- GPGME before version 2.3.0
- Current fixed version
- GPGME 2.3.1
- Legacy fixed version
- GPGME 1.24.4
- Windows package
- Gpg4win 5.1.2 bundles the fixed library
What people are saying
remote code execution cannot be ruled out