GnuPG Security Advisory for GPGME
gdgghhhhh
247 points
98 comments
November 21, 2026
Related Discussions
Found 5 related stories in 194.6ms across 13,334 title embeddings via pgvector HNSW
- Updated GPG Key for Signing Firefox and Thunderbird Releases csmantle · 23 pts · August 11, 2026 · 54% similar
- Debian apt security update: man-in-the-middle arbitrary code execution vesinisa · 98 pts · November 04, 2026 · 48% similar
- Debian apt security update (man-in-the-middle) SG- · 140 pts · November 04, 2026 · 47% similar
- Oracle Security Alert Advisory – CVE-2026-91403 (eMudhra cert revocation) rayhaanj · 24 pts · October 21, 2026 · 47% similar
- GCC AI Policy Announcement signa11 · 31 pts · September 13, 2026 · 47% similar
Discussion Highlights (13 comments)
miduil
This vulnerability was discovered by Johan Carlsson and we were informed by GitLab on 2026-11-12. Initially we set 2026-11-25 for a coordinated disclosure; due to the new Ruby2Shell bug GitLab had to update earlier and thus we also disclosed the GPGME bug on 2026-11-20. I guess pretty important for GitLab since it supports signed commits, code execution in that path is pretty bad. You can find the GitLab Omnibus related patch here: https://gitlab.com/gitlab-org/omnibus-gitlab/-/commit/279ac3...
legsrunny
more or less than 0 impacted systems?
uptrails
Reportedly fixed by Red Hat 5 years ago based on the output from conventional tools, but missed by upstream: https://gitlab.com/redhat/centos-stream/rpms/gpgme/-/blob/c9...
usr1106
What are practical attack vectors for Linux workstations and servers? The masses of internet users don't know what GPG is. I'd caim the majority of software developers don't have a GPG key and never explicitly verify any signature. But packages of many distros are verified using GPG. Is the vulnerable component involved or not?
mik1998
It's a double free bug, not an RCE chain. Are these vulnerability reports intentionally overstated?
mmsc
The vulnerability is in GpgME (the library), not GnuTLS (the library).
usr1106
Editorialized submission title to be better bait. The correct title is: GnuPG Security Advisory for GPGME
Velocifyer
This is a reminder that Seqouia-PGP exists, and its 'sq' CLI is way more intuitive.
IshKebab
Luckily nobody uses it!
fock
so essentially look at the key before? (and hope your program does not have another RCE...)
tombardier
"We are pleased to announce..."
wannabe44
All software using a GPGME version prior to 2.3.0 either as shared libary, DLL, or statically linked is affected. Examples of software using GPGME are - Gpg4win - GnuPG Desktop - GnuPG VS-Desktop - Most mail clients - Many XMPP clients - Samba - Flatpack I assume this is in "gpgme" and doesn't affect apt etc? Can someone confirm?
dehrmann
It's becoming clear that humans have no business writing C/C++ without Rust-level tooling around it to prevent these things.