SecOraLens
CriticalCVECVE-2026-129975

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

The Hacker News·Source published ·1 min read

What happened?

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.

Key details

  • A malicious OpenPGP key with an unusually long user ID can trigger a critical memory bug in GPGME.
  • The flaw is a double free in read_status() and read_colon_line() routines that process status lines and key listings from GnuPG.
  • When input runs long, routines move data to a larger buffer but record the new address only if they finish without errors, leaving a dangling pointer on error.
  • The bug affects all software using GPGME before version 2.3.0, including mail clients, XMPP clients, Samba, and GnuPG desktop packages.
  • The vulnerability was found by Johan Carlsson and reported by GitLab; disclosure was moved up due to the Ruby2Shell bug.

What is affected?

  • All software using GPGME before version 2.3.0, including shared libraries, Windows DLLs, and statically linked copies.
  • Examples include most mail clients, many XMPP clients, Samba, Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop packages.

How do I fix or mitigate it?

  1. Applications with bundled or statically linked GPGME copies need their own rebuilt releases; system library updates do not reach them.

Summarised by SecOraLens from The Hacker News. Always read the original source before acting. How SecOraLens verifies advisories.

What to do next

For CISOs and SOC leads

Brief your board. Brief your team.

Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.