Skip to content

Vulnerabilities & Patches

GnuPG discloses critical GPGME memory flaw triggered by malicious OpenPGP keys

The Hacker News reported that CVE-2026-129975 lets a maliciously crafted OpenPGP key with a long user ID expose data from affected applications.

https://breach-signal.com/vulnerabilities/gnupg-discloses-critical-gpgme-memory-flaw-cve-2026/

Share

Key facts

  • The Hacker News reported on November 21, 2026 that GnuPG disclosed a critical memory corruption bug in GPGME.
  • GnuPG said the flaw could expose data from affected applications.
  • No attacks exploiting this flaw have been reported by the project.
  • All software using GPGME before version 2.3.0 is affected.

The Hacker News reported on Nov. 21, 2026 that GnuPG disclosed a critical memory corruption bug in GPGME, triggered by a maliciously crafted OpenPGP key with an unusually long user ID.

The Hacker News reported that GPGME is the standard library programs use to work with GnuPG. All software using GPGME before version 2.3.0 is affected, whether the library loads as a shared library or a Windows DLL, or is statically linked into software. Bundled and statically linked copies are affected too, and they do not receive updates from the system’s shared library. Applications containing bundled or statically linked copies need their own rebuilt releases.

The Hacker News reported that the project lists most mail clients as affected software. It also lists many XMPP clients, Samba, its Gpg4win package, its GnuPG Desktop package and its GnuPG VS-Desktop package. Gpg4win 5.1.2 bundles the fixed library on Windows.

The Hacker News reported that the flaw is a double free in which the same memory gets released twice. It sits in two routines named read_status() and read_colon_line(), which read status lines and key listings returned by GnuPG. When input runs long, the routines move data to a larger buffer. The routines store the new address only when they finish without errors, so a pointer to already freed memory remains when an error occurs between steps.

Cleanup frees the memory a second time, the project’s tracker entry details.

The Hacker News reported that Johan Carlsson discovered the flaw. GitLab reported the flaw to the project last week. The advisory says disclosure was set for Nov. 25. The company was forced to update earlier by the new Ruby2Shell bug.

The Hacker News reported that GnuPG said the flaw could expose data from affected applications, and noted that remote code execution cannot be ruled out. No attacks exploiting this flaw have been reported by the project.

The Hacker News reported that GPGME 2.3.1 is the fixed library version and was released this week. GPGME version 2.3.0 was never publicly available. The advisory tells users of shared libraries or DLLs to update to GPGME 2.3.1 from the project’s official downloads and security advisory.

The Hacker News reported that Gpg4win release notes call the issue severe and urge updating as soon as possible. The advisory includes a patch for older versions unable to move to 2.3.1.

The Hacker News reported that fixed release 1.24.4 exists for the legacy branch, though legacy release notes say the project cannot promise every security patch for the branch. The Hacker News reported that no update is needed for GPGMEPP and GPGMEQT. The advisory offers no interim workaround for software unable to update yet.

Was this helpful?

Join the discussion

Please read our Comment Policy before commenting. First-time comments are held for moderation. By posting a comment you agree to our Terms of Use and Privacy Policy, which explain how your name, email address and comment are used.

Your email address will not be published. Required fields are marked *