GPGME double-free needs a consumer inventory and updates
Identifiers: CVE-2026-129975
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
GnuPG disclosed CVE-2026-129975 (T8557) on November 20, 2026, a double-free memory-handling bug in GPGME (GnuPG Made Easy). An application that uses the library can reach the bug when it processes malicious OpenPGP data. The upstream advisory covers GPGME versions before 2.3.0, and 2.3.0 was never publicly available, so the public mainline fix is GPGME 2.3.1. GnuPG's legacy maintainer has also released 1.24.4 as an explicit fix for the older line, while warning that future security patch coverage for that line is not guaranteed. Vendor backports can carry smaller package versions, for example Debian 13 (trixie) gpgme1.0 1.24.2-3+deb13u1 and Debian 12 (bookworm) 1.18.0-3+deb12u1, so judge each copy by its own package or update channel rather than by comparing it with the upstream number. The Gpg4win project advisory states that Gpg4win 5.1.2 includes the fix for Windows desktops. The reviewed sources do not establish real-world exploitation.
Impact
Malicious OpenPGP data processed through an affected GPGME copy can corrupt memory. The vendor describes potential exposure of data held by the affected application and says code execution cannot be ruled out. The practical scope depends on which process embeds the library and what data that process holds.
Who is affected
You are affected only when both conditions hold: the system has a GPGME copy without the fix for its package or update channel, whether as a shared library, a dynamic Windows library, or a bundled or statically linked copy inside an application or container image, and a consumer passes untrusted OpenPGP material to that copy, such as inbound signed data. Not every mail client, PGP command-line tool, GitLab deployment, web server, or signature-verification task relies on GPGME. Which component and which data paths are involved is an inventory question, not an assumption.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| GPGME | Upstream before 2.3.0. Legacy fix and distribution backports have separate versioning. | 2.3.1 (upstream mainline), 1.24.4 (legacy) |
Exploitation evidence
Exploitation not established. No real-world exploitation is established in the reviewed primary sources as of November 22, 2026. The flaw is a double-free reached when an application that embeds GPGME processes malicious OpenPGP data. The vendor's own assessment of potential data exposure and possible code execution is the reason for prompt remediation.
Actions
- Identify the components that actually use GPGME and pass untrusted OpenPGP material to it, across installed packages, application and container images, and bundled or statically linked copies, and record the update channel for each copy.
- Apply the fix for each channel: the vendor or distribution fixed package where one exists, GPGME 2.3.1 for direct upstream mainline builds, and 1.24.4 only as the explicit fix for the legacy line, judging each copy by its own vendor advisory and package revision rather than by the upstream version number.
- For bundled images and static copies, obtain the vendor's rebuilt build or rebuild against a fixed library, then redeploy.
- Restart or redeploy every affected process after updating, because a shared library update alone does not reach already-running programs or bundled and static copies.
- Confirm the normal signature workflow still works with benign signed material, and check that vendor support information and the installed package revision cover each deployment.
Unknowns
- Whether any of your deployments actually route untrusted OpenPGP data through GPGME, and which data paths are involved.
- Whether a fixed package is available for every distribution, vendor image, and bundled copy you run, since only GnuPG and Debian releases were verified for this briefing.
- Whether this flaw has been abused anywhere in practice, since the reviewed sources do not confirm exploitation.
- How long the legacy 1.24 line will continue to receive security fixes.
Sources
- GnuPG project https://lists.gnupg.org/pipermail/gnupg-announce/2026q4/000517.html
- GnuPG project https://dev.gnupg.org/T7659.html
- Debian Security Tracker https://security-tracker.debian.org/tracker/CVE-2026-129975
- Gpg4win project https://www.gpg4win.org/change-history.html
Change history
- — Published: November 22, 2026: Briefing published for CVE-2026-129975 in GPGME after rechecking the GnuPG announcement, the GnuPG issue tracker, and the Debian security tracker. Recorded 2.3.1 as the public mainline fix, 1.24.4 as an explicit legacy-line fix without future coverage guarantees, and Debian backports under smaller package versions. Applicability tied to each copy's own package or update channel and to consumers that pass untrusted OpenPGP material to it. No real-world exploitation confirmed.