Security · High impactFan score 22 · Tier C4 sources
Fwd: Re: [Announce] GnuPG Security Advisory for GPGME (T8557,CVE-2026-129975)
The Brief · written from 4 sources
- GnuPG announced a critical memory-safety bug in its GPGME library, tracked as CVE-2026-129975, on 2026-11-20.
- A malicious OpenPGP key with an unusually long user ID can trigger the bug.
- Sources say it could be used to steal data from applications that use GPGME, and a fix has been released.
Why it matters
Many applications rely on GPGME to handle OpenPGP keys, so a crafted key imported by one of them can expose its data. Developers who ship or depend on GPGME-based software should check whether they are affected and apply the fixed release.
Who’s affected
- Developers and maintainers of applications using GPGME
- Email client and XMPP client users and packagers
- Flatpak and Samba users of GPGME
What to do
- Update GPGME to the patched release once it is available in your distribution or package source.
- Check whether your applications link against GPGME and rebuild or update them.
- CVE-2026-129975
- #security
- #gnupg
- #gpgme
- #openpgp
- #cve
- #memory-safety
Posted by Sam James on Nov 21 Todd Zullinger points out something unfortunate: RH had this patched downstream years ago. Werner, I assume that was never sent to you? -------------------- Start of forwarded message -------------------- Date: Fri, 20 Nov 2026 20:06:51 -0500 To…
Timeline
Full coverage · 4 sources
- 3h ago ↗
- 3h ago ↗
Open Source Security
Fwd: Re: [Announce] GnuPG Security Advisory for GPGME (T8557,CVE-2026-129975)
- 17h ago ↗
Open Source Security
Fwd: GnuPG Security Advisory for GPGME (T8557,CVE-2026-129975) - 17h ago ↗