Skip to content
NewA calmer, faster ZeroHour

Critical GPGME double-free can leak app data via long OpenPGP keys

Original title: GnuPG Warns Critical GPGME Flaw Could Expose App Data via Malicious OpenPGP Keys

The Hacker News ()2 min read1
Part of a story covered by 2 sourcesGnuPG fixes GPGME double-free that can leak application dataMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

Update shared copies to GPGME 2.3.1 or legacy 1.24.4; Gpg4win needs 5.1.2, and bundled copies need rebuilds.

The GnuPG project warned that a malicious OpenPGP key with an unusually long user ID can trigger a double-free in GPGME before 2.3.0. CVE-2026-129975 can expose data from applications using the library, and remote code execution cannot be ruled out. GnuPG has not reported attacks. Fixes are GPGME 2.3.1, legacy 1.24.4, and Gpg4win 5.1.2; statically linked copies need their own rebuilds, and no workaround is offered.

Unconfirmed: Which applications pass signed data to GPGME without a manual key import is not stated.

Key facts
  • The bug is in read_status() and read_colon_line() when status or key data is long.
  • GPGME 2.3.0 was never publicly available; the fixed library release is 2.3.1.
  • GPGMEPP and GPGMEQT do not need an update.
  • Johan Carlsson found the flaw; GitLab reported it last week.
  • Disclosure moved up from November 25 because of the Ruby2Shell update.
Security assessment · AI, from the articleNo known exploitation

Impact: Data theft from apps using GPGME; RCE not ruled out

ProductAffectedFixed in
GnuPG GPGMEbefore 2.3.02.3.1
GnuPG GPGMElegacy branch1.24.4
GnuPG Gpg4win—5.1.2
What to do
  1. 1.Update shared or DLL copies of GPGME to 2.3.1.
  2. 2.Install Gpg4win 5.1.2 on Windows, or legacy GPGME 1.24.4 if 2.3.1 is unavailable.
  3. 3.Rebuild applications that bundle or statically link GPGME; shared-library updates do not cover them.
Analyze CVE-2026-129975 with Vani AIImpact, affected versions, exploitation, mitigations and detection

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2026-129975
———

From the original article

2 min read at thehackernews.com

A malicious OpenPGP key with an unusually long user ID can trigger a critical memory bug in GPGME, the standard library that programs use to work with GnuPG. The GnuPG project warned yesterday that the flaw could be used to steal data from affected applications and has released fixed versions. The bug, tracked as CVE-2026-129975, affects all software that uses GPGME before version 2.

The Hacker News

thehackernews.com

Read the full article at The Hacker News

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.