Skip to main content
Mallory
UnratedVulnerability

CVE-2026-129975: Double-free in GPGME OpenPGP key processing

Updated today
Trending this week#52of 431,975 vulnerabilities
Mention activity · 30 days51 mentions · peak 45 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-129975CWE-415

CVE-2026-129975 is a critical double-free vulnerability in GPGME, a library used by applications to interact with GnuPG. Processing an OpenPGP key with a crafted, very long user ID can trigger faulty buffer management in the read_status() and read_colon_line() routines, which process GnuPG status output and key listings. These routines reallocate a buffer but defer updating the owning context's pointer until successful completion. An intervening error can leave the context referencing freed memory, which is freed again during cleanup. Intervening allocations can prevent common allocator double-free checks from detecting the condition. Exploitation can disclose application data or cause denial of service; arbitrary code execution is considered possible but has not been demonstrated. Unpatched GPGME releases before 2.3.0 are affected across shared-library, Windows DLL, bundled, and statically linked deployments. Version 2.3.0 was not publicly released; 2.3.1 is the fixed current release.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Processing malicious OpenPGP key material can expose data held by the affected application or crash it. Potential arbitrary code execution could compromise the application within its execution privileges, although remote code execution has not been demonstrated. Exposure extends to applications incorporating vulnerable GPGME copies, including mail clients, XMPP clients, Samba, and GnuPG desktop distributions. No active exploitation or publicly available exploits were reported at disclosure.

Mitigation

If you can’t patch tonight, do this now.

No validated interim workaround has been identified. Updating or applying the upstream patch is the established corrective action.

Remediation

Patch, then assume compromise.

Upgrade to GPGME 2.3.1 or a vendor package containing the fix. GPGME 1.24.4 provides a fixed legacy-branch release. For Debian stable (trixie), upgrade the gpgme1.0 packages to 1.24.2-3+deb13u1 or later fixed versions. Windows users can obtain the corrected library through Gpg4win 5.1.2; updated GnuPG Desktop and GnuPG VS-Desktop releases were also announced. Rebuild statically linked applications against a fixed GPGME version and update applications that bundle their own copy; updating the system library alone does not fix these deployments. If upgrading is not possible, apply the upstream security patch or an equivalent vendor backport. GPGMEPP and GPGMEQT do not independently require updates for this issue.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-129975 exploited in the wild?
As of Nov 21, 2026, Mallory has no reports of CVE-2026-129975 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-129975?
As of Nov 21, 2026, Mallory has found no public exploit for CVE-2026-129975.
Is there a patch for CVE-2026-129975?
Upgrade to GPGME 2.3.1 or a vendor package containing the fix. GPGME 1.24.4 provides a fixed legacy-branch release.
Activity feed

Recent activity

51 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
the hacker newsNews · Nov 21, 2026GnuPG Warns Critical GPGME Flaw Could Expose App Data via Malicious OpenPGP KeysA critical double-free vulnerability in GPGME's read_status() and read_colon_line() routines can be triggered by a malicious OpenPGP key with an unusually long user ID. Errors during buffer expansion can leave a stale pointer that cleanup frees again. Exploitation could expose application data, and remote code execution cannot be ruled out. Fixed releases are GPGME 2.3.1 and legacy version 1.24.4; Gpg4win 5.1.2 bundles the fix. Bundled or statically linked copies require application-specific rebuilt releases. No exploitation has been reported, and the advisory provides no interim workaround.Read more ↗tenable cloud security pluginsNews · Nov 21, 2026Alpine: multiple gpgme packages: security update to 2.3.1-r0 | Tenable®A vulnerability associated with Alpine Linux gpgme packages. The page identifies a security update to version 2.3.1-r0 and states that no known exploits are available. The vulnerability's underlying mechanism is not described.Read more ↗tenable nessus pluginsNews · Nov 20, 2026Debian dla-4924 : libgpgme-dev - security update | Tenable®A vulnerability covered by Debian security update DLA-4924 for libgpgme-dev and associated packages. The listed CVSS v3 vector indicates unauthenticated network exploitation without user interaction and high confidentiality, integrity, and availability impacts. The content does not describe the underlying flaw.Read more ↗tenable nessus pluginsNews · Nov 20, 2026Linux Distros Unpatched Vulnerability : CVE-2026-129975 | Tenable®An unpatched vulnerability associated with the Debian gpgme1.0 package. The listed CVSS v3 vector indicates network exploitation without authentication or user interaction, with high confidentiality, integrity, and availability impacts. No known exploits are available according to the plugin.Read more ↗
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity46Community discussion across Reddit, Mastodon, and other social sources.