RCE in Gnupg (lists.gnupg.org)

196 points by gdgghhhhh 12 hours ago

uptrails 9 hours ago

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

gdgghhhhh 8 hours ago

sandos an hour ago

How is this even possible?

"when it was noticed by a Coverity scan:"

It was found by static analysis FIVE years ago, but never re-found? That is really odd. I thought people were running every kind of commercial scanning tool on OSS for free most of the time.

c-hendricks 6 hours ago

Hurray for endless distro forks

christophilus 6 hours ago

Rh is kind of the canonical distro, though, as much as there is such a thing. I’m surprised this was never upstreamed.

gpvos an hour ago

BadBadJellyBean 2 hours ago

cowlevel an hour ago

throooooo 5 hours ago

miduil 10 hours ago

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

dehrmann 2 hours ago

It's becoming clear that humans have no business writing C/C++ without Rust-level tooling around it to prevent these things.

mik1998 8 hours ago

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

cowlevel an hour ago

AI is doing quite well at automating the escalation of small memory bugs (which can usually theoretically cause RCEs) into actual RCE exploits. This bug has a similar nature to php2shell.

InsidiousWombat 6 hours ago

Yes, the actual post just implies possibility

> Exploiting this bug to mount an Remote Code Execution attack (RCE) can't be ruled out.

mhluongo 5 hours ago

Today's LLMs can often escalate to RCE, so it makes sense to assume the worst.

slim 2 hours ago

it does not make sense to say RCE for something that does not have an open port on the system

rubendev 2 hours ago

gertop 4 hours ago

It makes sense to assume the worst, then try to achieve it. And only if you achieve it so you tag it as such. You can't announce vulnerabilities to the world based on vibes of what it might do....

"Yeah this is a classic double free. We can't think of a way to transform it into a RCE or something like that, we've also failed at having LLMs do it so far. but in the current climate it could happen so we humbly ask the tag of most dangerous vulnerability please. Not just this disclaimer. We want 9.9 CVE that says RCE!!"

This is ridiculous.

gdgghhhhh 8 hours ago

Sending somebody a signed message and trigger a double free is a prime example for RCE

kuroguro 8 hours ago

RCE might be possible, you still need to overlay something useful in the freed memory and bypass ASLR.

Deeg9rie9usi 8 hours ago

dboreham 4 hours ago

gsich 8 hours ago

poc needed.

Deeg9rie9usi 8 hours ago

wannabe44 3 hours ago

    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?

usr1106 8 hours ago

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?

kodoman 6 hours ago

> But packages of many distros are verified using GPG. Is the vulnerable component involved or not?

Debian uses it last time I was on a Debian system And I think all Debian based distros that don't modify apt will essentially use GPG to verify the packages as well.

I think it's one of the those programs that pop up in a lot of different things. Personally I use it a fair amount and even use the Symmetric encryption features for some files and for personal password management.

I do think developer are moving away from it thought I agree (and for various reasons that are good).

lazka 7 hours ago

Arch Linux uses gpgme to verify downloaded packages (and optionally, package databases) for example.

firesteelrain 5 hours ago

It’s used a lot in commercial for code signing. We use it with Thales HSMs (there are other things in the middle)

usr1106 5 hours ago

Are you sure? (I am not) The announcement says gpgme. Is that the same thing used for basic signatures?

OJFord 8 hours ago

Potentially package update/installation? A lot of people use gpg without knowing it.

It's specifically in 'GPGME' though, so more limited scope I think.

capitol_ 7 hours ago

A lot of those places have switched out the gnupg PGP implementation with sequoia-openpgp.

usr1106 5 hours ago

usr1106 7 hours ago

That was my question. Where is gpgme used? Any "unexpected" places?

gdgghhhhh 8 hours ago

PGP mail?

Geezus_42 8 hours ago

Which almost no one uses.

gdgghhhhh 8 hours ago

tombardier 4 hours ago

"We are pleased to announce..."

gpvos an hour ago

Bugfixes are good.

usr1106 7 hours ago

Editorialized submission title to be better bait.

The correct title is: GnuPG Security Advisory for GPGME

g-b-r 6 hours ago

Which wouldn't tell us anything before checking the link

fn-mote 6 hours ago

The current title is "RCE in Gnupg". A more appropriate title would be "Double free produces posible RCE in GnuPG". The non-editorialized title would also be better because it does not claim there is an RCE that is not known to exist.

"Probable RCE in GnuPG clients" would be appropriate.

When someone posts a Claude POC, then the situation is different.

msm_ 41 minutes ago

g-b-r 6 hours ago

fock 6 hours ago

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

Velocifyer 7 hours ago

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

mmsc 8 hours ago

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

legsrunny 10 hours ago

more or less than 0 impacted systems?

IshKebab 7 hours ago

Luckily nobody uses it!