Security

GnuPG fixes a critical GPGME double-free flaw that a booby-trapped OpenPGP key can trigger; version 2.3.1 is the fix

GPGME 2.3.1 fixes a critical double free (CVE-2026-129975) that a crafted OpenPGP key with a very long user ID can trigger.

By ·

The GnuPG project released GPGME 2.3.1 to fix CVE-2026-129975, a critical double-free bug that a crafted OpenPGP key with an unusually long user ID can trigger. GPGME is the library applications use to call GnuPG, so the advisory of 20 November affects every program that links it.

The essentials

Credit and timing

Johan Carlsson discovered the flaw and GitLab reported it to GnuPG, according to Mallory. Werner Koch signed the advisory, which Runtime Wire says was disclosed five days earlier than planned.

What is not established

Summary table

Summary table
PointWhat is stated as of November 21, 2026Source
Advisory date20 November 2026Runtime Wire
Fixed versionGPGME 2.3.1The Hacker News
Windows bundleGpg4win 5.1.2InfosecToday

FAQ

How do I fix the GPGME flaw?

Update to GPGME 2.3.1 (or Gpg4win 5.1.2 on Windows), and rebuild statically linked programs against the fixed library.

Sources

Spotted an error in this article? Report it · Our corrections policy

OrigoTech logo

New: the app iPhone & iPad

OrigoTech is now an iPhone and iPad app

Read the articles natively, with “New” markers on unread ones, local search and offline reading of what you have already loaded. Free, no account, iOS 17 or later; ads appear between articles.

Rekha icon: a house drawn in a single stroke

From the same author Self-promotion

An Eulerian path, drawn with your finger

Rekha, the iPhone game by OrigoTech's author: connect every dot in a single stroke without tracing the same link twice, across 500 drawings that are all solvable.

The OrigoTech newsletter

A sourced weekly digest of AI tool news.

Read next