Skip to content
NewA calmer, faster ZeroHour
StoryVulnerabilityhigh

GnuPG fixes GPGME double-free that can leak application data

2 sources · 2 articlesFirst reported Updated ()1
What's new

First merged summary.

Merged summary · x-ai/grok-4.7 · rewritten as coverage arrivesSummaries by Vani AI

GnuPG shipped GPGME 2.3.1 for a double-free that can leak data from apps processing crafted OpenPGP keys; attacks are unreported.

GnuPG released GPGME 2.3.1 to fix CVE-2026-129975, a double free when status lines or key listings are read, present in every earlier public version. A crafted OpenPGP key with a very long user ID can leave a stale pointer that is freed twice; the project says this can expose application data, and remote code execution cannot be ruled out. Shared copies should move to 2.3.1 or legacy 1.24.4, and Gpg4win to 5.1.2; statically linked copies need rebuilds. Version 2.3.0 was never public, and GnuPG has not reported attacks. Lobsters says a patch is offered for older builds; The Hacker News says no workaround is offered.

Key facts
  • CVE-2026-129975 is a double free in read_status() and read_colon_line().
  • Fixed releases are GPGME 2.3.1, legacy 1.24.4, and Gpg4win 5.1.2.
  • Mail clients, many XMPP clients, and Samba are named as users.
  • GPGMEPP and GPGMEQT do not need a separate update.
  • Johan Carlsson found the bug; GitLab notified GnuPG on November 12.
  • Disclosure moved from November 25 to November 20 after a Ruby2Shell update.
Analyze CVE-2026-129975 with Vani AIImpact, affected versions, exploitation, mitigations and detection

Timeline

dated events in the reporting · oldest first
  1. Nov 12, 2026GitLab notified GnuPG of the GPGME flaw. · Lobsters
  2. Nov 20, 2026GnuPG disclosed the GPGME security advisory. · Lobsters

What each outlet adds

beyond the shared facts
  • LobstersNames affected applications and a patch for older builds.
  • The Hacker NewsAdds legacy 1.24.4, required rebuilds, and no reported attacks.

Coverage

oldest first · one row per article · UTC
  1. · 1d ago Lobsters · securityFirst report

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

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

  2. · 1d ago The Hacker News

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

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

Vulnerabilities in this story

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2026-129975
———