Back to Feed
VulnerabilitiesNov 21, 2026

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

GnuPG warns of critical GPGME flaw that could expose app data via malicious OpenPGP keys.

A critical memory bug in the GPGME library, tracked as CVE-2026-129975, can be triggered by a malicious OpenPGP key with an unusually long user ID. This flaw could potentially lead to data theft from affected applications, and remote code execution cannot be ruled out. GnuPG has released fixed versions of GPGME (2.3.1) and related packages like Gpg4win (5.1.2).

AI summary of the linked source. Not reviewed by an editor. How this works

Vendor Watch

Run GnuPG?

Get an email when a new story names GnuPG, usually within the hour.

Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy

The lesson from this incident

Full lesson

A critical memory corruption vulnerability (CVE-2026-129975) in the GPGME library allows an attacker to trigger a flaw simply by supplying a malicious OpenPGP key with an unusually long user ID, requiring no authentication or privileged access. This type of input-validation failure in a widely-used cryptographic library is particularly dangerous because GPGME underpins many applications that handle sensitive encrypted data. If exploited, attackers could steal application data or potentially achieve remote code execution. The fact that GnuPG has already released patched versions (GPGME 2.3.1, Gpg4win 5.1.2) means the primary risk now lies with organizations that delay applying these updates.

What helps against this

How we list vendors

Indicators of Compromise

Addresses and file hashes are copied from the publisher's page by pattern matching. Names are picked by AI. On stories from before 17 November 2026, some addresses and hashes were picked by AI too. Not reviewed by an editor. How this works

  • cve: CVE-2026-129975

Entities

GPGME (product)GnuPG (vendor)Gpg4win (product)