Skip to content
NewA calmer, faster ZeroHour

GPGME before 2.3.1 double-free via long OpenPGP user ID (CVE-2026-129975)

Original title: GnuPG Security Advisory for GPGME (T8557,CVE-2026-129975)

Lobsters · securityby lists.gnupg.org via rw-rw-rw ()4 min read2 · 1 read
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

Versions before 2.3.0 can leak data from apps that process a crafted key; remote code execution is not ruled out.

GnuPG released GPGME 2.3.1 to fix a double free in status-line and key-listing reads, present in every earlier public version. A crafted, very long OpenPGP user ID can leave a stale pointer that is freed twice, which the project says can exfiltrate data when applications process signed data. Remote code execution cannot be ruled out. Gpg4win 5.1.2 includes the fix; version 2.3.0 was never public.

Unconfirmed: The advisory does not confirm remote code execution or in-the-wild exploitation.

Key facts
  • Johan Carlsson found the bug; GitLab notified GnuPG on November 12.
  • Disclosure moved to November 20 after GitLab's earlier Ruby2Shell update.
  • Mail clients, many XMPP clients, and Samba are named as affected users.
  • GPGMEPP and GPGMEQT do not need a separate update.
  • A patch is offered for older GPGME builds that cannot be upgraded.
Security assessment · AI, from the article

Impact: Double free can exfiltrate data; RCE not ruled out

ProductAffectedFixed in
GnuPG GPGMEall versions prior to 2.3.02.3.1
GnuPG Gpg4win—5.1.2
What to do
  1. 1.Update the GPGME shared library to 2.3.1.
  2. 2.Rebuild statically linked binaries against GPGME 2.3.1.
  3. 3.If GPGME cannot be updated, apply the attached patch.
Analyze CVE-2026-129975 with Vani AIImpact, affected versions, exploitation, mitigations and detection

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2026-129975
———

Indicators of compromise

auto-extracted · verify before use · export allAll
TypeIndicatorContext
sha11134a407b50204ee6fb9efaa6e1451c2460e543erg/download/integrity_check.html The checksum for gpgme is: 1134a407b50204ee6fb9efaa6e1451c2460e543e gpgme-2.3.1.tar.bz2 *Thank you all* Your GnuPG hackers p.s.

From the original article

4 min read at lists.gnupg.org

We are pleased to announce the availability of a new GPGME release: version 2. 3. 1.

Lobsters · security

By lists.gnupg.org via rw-rw-rw · lists.gnupg.org

Read the full article at Lobsters · security

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.