Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilityendpoint-software-vulnerabilitywidely-deployed-product-advisory

Critical GPGME Double-Free Flaw Could Expose Application Data via Malicious OpenPGP Keys

Vulnerability Disclosure · 4 sources · Updated 9h ago · First seen Nov 20, 2026

Critical GPGME Double-Free Flaw Could Expose Application Data via Malicious OpenPGP Keys

GnuPG disclosed CVE-2026-129975, a critical double-free vulnerability in its GnuPG Made Easy (GPGME) library that can be triggered by an OpenPGP key containing an unusually long, specially crafted user ID. The project warned that exploitation could steal data from affected applications; remote code execution cannot be ruled out but remains unconfirmed, and no exploitation has been reported. The flaw affects all prior upstream versions, potentially exposing email and XMPP clients, Flatpak, Samba, and GnuPG desktop packages that use shared, DLL, bundled, or statically linked copies of GPGME.

Update immediately to GPGME 2.3.1 or the fixed legacy release 1.24.4, and deploy relevant application updates, including Gpg4win 5.1.2 and updated GnuPG Desktop and VS-Desktop packages. Bundled or statically linked copies require application-specific updates; replacing the system library alone will not remediate them. In the oss-sec discussion, Todd Zullinger reported that Red Hat Enterprise Linux 9 already carried a downstream fix developed roughly five years earlier following a Coverity finding, but that the fix had not reached upstream or Fedora and was absent from earlier and later RHEL releases. Administrators should therefore verify package-specific patch status rather than rely solely on version numbers.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

5 events · Nov 20, 2026
  1. Reported Nov 21, 202611h ago

    GPGME 1.24.4 supplies a legacy-branch fix

    GPGME 1.24.4 provides a fix for the legacy branch, and the advisory offers a patch for older versions that cannot migrate to GPGME 2.3.1. GnuPG cautioned that the legacy branch is not guaranteed to receive every security patch.

    GnuPG Warns Critical GPGME Flaw Could Expose App Data via Malicious OpenPGP Keys
  2. Reported Nov 21, 202611h ago

    Johan Carlsson discovers the GPGME flaw; GitLab reports it to GnuPG

    Johan Carlsson discovered the vulnerability, and GitLab reported it to the GnuPG project. The planned disclosure was subsequently accelerated because the Ruby2Shell bug forced GitLab to update earlier.

    GnuPG Warns Critical GPGME Flaw Could Expose App Data via Malicious OpenPGP Keys
  3. Reported Nov 21, 202611h ago

    RHEL 9 receives a downstream fix after a Coverity finding

    According to Todd Zullinger, a Coverity scan identified the double-free issue and RHEL 9 received a downstream fix approximately five years before the November 2026 discussion. The fix was not shared upstream or with Fedora and was absent from earlier and later RHEL releases.

    oss-sec: Fwd: Re: [Announce] GnuPG Security Advisory for GPGME (T8557,CVE-2026-129975)
  4. Nov 20, 20262d ago

    GPGME 2.3.1 and updated GnuPG desktop packages announced

    Werner Koch announced GPGME 2.3.1 as a security release fixing the vulnerability and urged users to update immediately. Updated Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop releases were announced alongside it because they use GPGME.

    GnuPG's GPGME Affected By Critical Security Bug In Turn Affecting Mail Clients, Flatpak - Phoronix
  5. Nov 20, 20262d ago

    GnuPG discloses critical GPGME double-free vulnerability

    Werner Koch disclosed CVE-2026-129975, a critical double-free triggered by an OpenPGP key with a specially crafted, very long user ID. GnuPG warned that exploitation could expose application data and that remote code execution could not be ruled out, although it had not reported attacks exploiting the flaw.

    GnuPG's GPGME Affected By Critical Security Bug In Turn Affecting Mail Clients, Flatpak - Phoronix
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.