GnuPG Security Advisory For GPGME
AIThis post was created with the assistance of artificial intelligence (AI).

TL;DR

GnuPG released GPGME 2.3.1 on Nov. 20, 2026, fixing CVE-2026-129975, a double-free vulnerability triggered by a crafted, very long OpenPGP user ID. The project says applications using older GPGME versions may be affected and recommends upgrading; data exfiltration is possible, while remote code execution cannot be ruled out.

GnuPG released GPGME 2.3.1 on Nov. 20 to fix CVE-2026-129975, a critical double-free vulnerability in earlier versions of the library. The project says an attacker could use a crafted OpenPGP key with a very long user ID to trigger the bug and potentially exfiltrate data from applications; it says a remote code execution attack cannot be ruled out.

Before you orderOffer from Amazon

Get privacy and security gear delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

In its security advisory, GnuPG said the flaw affects software using a GPGME version earlier than 2.3.1, whether the library is used as a shared library, a Windows DLL or is statically linked into an application. The advisory names mail and XMPP clients, Samba, Flatpak, Gpg4win, GnuPG Desktop and GnuPG VS-Desktop as examples of software that may use GPGME. The list is illustrative; users should check with the makers of their software to determine whether a particular product is affected.

The bug occurs while GPGME reads status lines and key listings from GnuPG. According to the advisory, the library allocates an initial 1,024-byte buffer and reallocates it when more space is needed. In some early-return conditions, the updated pointer is not saved to the context. The context can then retain a stale pointer and free the same memory again when released, causing a double free. GnuPG says the flaw may be used to exfiltrate application data, for example by sending signed data. It does not report confirmed exploitation or establish that remote code execution has occurred.

The project recommends updating the GPGME shared library to version 2.3.1. Developers with statically linked binaries need to rebuild them against the fixed version. For users who cannot upgrade, GnuPG says an attached patch can be applied to older versions. The advisory says there is no need to update GPGMEPP or GPGMEQT for this fix. The release also includes new constants for ML-KEM, ML-DSA and DL-THM algorithm mappings.

At a glance
announcementWhen: Announced Nov. 20, 2026; GPGME 2.3.1 is…
The developmentGnuPG has published GPGME 2.3.1 to fix a critical double-free vulnerability and advised users of affected software to update.

Exposure Across GPGME-Using Software

GPGME is a library used by applications to work with GnuPG cryptographic functions, so a flaw in it can reach beyond people who directly run GnuPG commands. The advisory’s examples span email and messaging clients, file-sharing software and GnuPG’s own desktop products. That makes checking the library version relevant to software vendors, system administrators and users who rely on those applications to handle signed or encrypted data.

The stated impact is a potential loss of confidentiality: GnuPG says crafted input could be used to exfiltrate data from applications. Its warning that remote code execution cannot be ruled out describes a possibility, not a confirmed outcome. The advisory does not provide evidence of attacks in the wild, and the available source does not quantify how many deployed products or users are affected. The practical response is to apply the release or a suitable patch and verify that statically linked products have been rebuilt.

Products Worth Considering

Logitech MX Mechanical Mini for Mac Wireless Keyboard, Space Gray

Logitech MX Mechanical Mini for Mac Wireless Keyboard, Space Gray

As an affiliate, we earn on qualifying purchases.

Disclosure and Fixed Release Timeline

GnuPG said the vulnerability was discovered by Johan Carlsson and that GitLab informed the project on Nov. 12, 2026. The project initially planned coordinated disclosure for Nov. 25. It said it moved the disclosure forward after GitLab had to publish earlier because of a separate issue it called the Ruby2Shell bug. GnuPG then announced the GPGME flaw and fixed release on Nov. 20.

The advisory identifies the internal tracking number as T8557 and assigns the flaw CVE-2026-129975. GnuPG described version 2.3.1 as the security fix and noted that version 2.3.0 was never publicly available. It also announced updated Gpg4win, GnuPG Desktop and GnuPG VS-Desktop releases. Gpg4win 5.1.2 includes the fixed GPGME version, according to the announcement.

“An immediate update is highly suggested.”

— GnuPG security advisory

Exploit Activity and Product Exposure

The advisory does not say whether attackers have exploited the flaw, identify affected products beyond examples, or quantify the number of exposed users. It also does not establish that the vulnerability has been used to achieve remote code execution; GnuPG says only that this outcome cannot be ruled out. The impact may depend on how a particular application uses GPGME and processes attacker-controlled keys or data, but the advisory does not provide product-by-product conditions.

It is also not clear from the announcement how quickly downstream software makers will ship updates or whether every affected package has already incorporated GPGME 2.3.1. Users should not assume that updating GnuPG alone fixes a separately bundled or statically linked copy of the library. The status of those application-specific updates remains dependent on their maintainers.

Update Libraries and Verify Packages

GnuPG’s immediate guidance is to install GPGME 2.3.1 through its download channels or use an updated package from the relevant distributor. Maintainers of statically linked applications should rebuild against the fixed release; those unable to upgrade can assess the patch supplied with the advisory. Windows users can check the announced Gpg4win 5.1.2 release, while users of other affected products should consult their software vendors or distribution maintainers for status.

GnuPG also provides signature files and integrity-check instructions for downloads. Administrators should verify the origin and integrity of packages and confirm which GPGME version their applications actually use. Further information may come from downstream vendors as they report whether their products bundle the library and when fixes are available.

Key Questions

What does GPGME 2.3.1 fix?

It fixes CVE-2026-129975, a double-free flaw in GPGME’s code for reading GnuPG status lines and key listings.

Who may be affected?

Software using GPGME versions before 2.3.1 may be affected, including some mail and XMPP clients, Samba, Flatpak and GnuPG desktop products. Check with the software maker or distributor to confirm whether a particular application includes the vulnerable library.

Can the flaw allow remote code execution?

GnuPG says remote code execution cannot be ruled out. The advisory does not confirm that such an attack has been achieved or report exploitation in the wild.

What should users and developers do?

Update to GPGME 2.3.1. Developers using a statically linked copy should rebuild their binaries against the fixed version; GnuPG also provides a patch for cases where an upgrade is not possible.

Does updating GPGMEPP or GPGMEQT matter for this fix?

The advisory says there is no need to update GPGMEPP or GPGMEQT to address this vulnerability.

Source: lists.gnupg.org

You May Also Like

Google Fixed More Chrome Bugs In June Than Over The Past Two Years, Thanks To AI

Google resolved a record number of Chrome bugs in June, surpassing the total from the previous two years, aided by artificial intelligence tools.

Social Media Security: Staying Safe on Social Platforms

In a world of digital connections, discovering essential strategies for social media security could be your key to staying safe online. What will you learn next?

Even the Secret Service won’t use company-issued phones

The U.S. Secret Service avoids using government-issued mobile phones, citing security concerns, raising questions about communication security practices.

Cybersecurity Budgeting: Getting More Protection per Dollar in 2025Business

Harness innovative cybersecurity strategies in 2025 to maximize protection per dollar—discover how to stay ahead in an ever-evolving threat landscape.