logoalt Hacker News

RCE in Gnupg

127 points • by gdgghhhhh • today at 8:32 AM • 41 comments • view on HN

Comments

uptrails • today at 11:27 AM

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...

➕ show 2 replies
miduil • today at 10:33 AM

       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...

mik1998 • today at 12:29 PM

It's a double free bug, not an RCE chain. Are these vulnerability reports intentionally overstated?

➕ show 2 replies
usr1106 • today at 12:16 PM

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?

➕ show 5 replies
mmsc • today at 12:35 PM

The vulnerability is in GpgME (the library), not GnuTLS (the library).

usr1106 • today at 1:16 PM

Editorialized submission title to be better bait.

The correct title is: GnuPG Security Advisory for GPGME

➕ show 1 reply
fock • today at 2:16 PM

so essentially look at the key before? (and hope your program does not have another RCE...)

IshKebab • today at 1:32 PM

Luckily nobody uses it!

Velocifyer • today at 1:24 PM

This is a reminder that Seqouia-PGP exists, and its 'sq' CLI is way more intuitive.

legsrunny • today at 11:01 AM

more or less than 0 impacted systems?