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.
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!!"
The mail says "Exploiting this bug to mount an Remote Code Execution attack (RCE) can't be ruled out.".
They didn't write this just for fun. gnupg usually downplays security issues.
We are having this debate right now. So it's far from over. Without PoC it's unclear if it's RCE or just overhyped bullshit. See PHP or Nginx "RCE" which required specific crafted settings for it to even work. A video is not a "PoC".
If you believe an LLM can generate an exploit for this - feel free to post one.
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?
> 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).
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.
"We are pleased to announce..."
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...
A little more details: https://www.openwall.com/lists/oss-security/2026/11/21/1
Hurray for endless distro forks
Rh is kind of the canonical distro, though, as much as there is such a thing. I’m surprised this was never upstreamed.
No Canonical makes Ubuntu. Jokes aside, Ubuntu and Debian are the most used distros by far.
You can find the GitLab Omnibus related patch here: https://gitlab.com/gitlab-org/omnibus-gitlab/-/commit/279ac3...
It's a double free bug, not an RCE chain. Are these vulnerability reports intentionally overstated?
Yes, the actual post just implies possibility
> Exploiting this bug to mount an Remote Code Execution attack (RCE) can't be ruled out.
Today's LLMs can often escalate to RCE, so it makes sense to assume the worst.
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.
Sending somebody a signed message and trigger a double free is a prime example for RCE
RCE might be possible, you still need to overlay something useful in the freed memory and bypass ASLR.
The mail says "Exploiting this bug to mount an Remote Code Execution attack (RCE) can't be ruled out.". They didn't write this just for fun. gnupg usually downplays security issues.
I'd say that is as accurate as they can be. Since it's a library and it's a heap bug they have no idea how a particular application will be affected.
It's still a critical bug, just would not call it a prime example of rce.
I mean, the blame is moreso on the title of this HackerNews submission. "RCE can't be ruled out" is not equivalent to "RCE in Gnupg"
it can't be ruled out that an RCE exists in other parts of this software either
Or any software...
"overlay something useful in the freed memory and bypass ASLR"
I thought we reached the point a few years ago where the assumed probability this can be done is 100% ?
poc needed.
IMHO, these days any kind of UB has to be considered exploitable by an LLM. The times of debating whether something is exploitable or not are over.
It's interesting to see how polarizing this comment is, it's being upvoted and downvoted in waves.
We are having this debate right now. So it's far from over. Without PoC it's unclear if it's RCE or just overhyped bullshit. See PHP or Nginx "RCE" which required specific crafted settings for it to even work. A video is not a "PoC".
If you believe an LLM can generate an exploit for this - feel free to post one.
I agree PoC's should be a requirement for all this exploits.
at the very least should be criteria for assigning "high", CVE spam is annoying enough as it is
Na, for years I've been seeing crap like this "well there is no exploit" and then a year later one is found.
Quit writing memory free errors in software. Prove your software is safe, not prove that it's not exploitable.
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?
> 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).
It’s used a lot in commercial for code signing. We use it with Thales HSMs (there are other things in the middle)
Are sure? The announcement says gpgme. Is that the same thing used for basic signatures?
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.
A lot of those places have switched out the gnupg PGP implementation with sequoia-openpgp.
Interesting. Can you give examples. The only places I have met sequoia were conference talks by their maintainer, probably founder.
That was my question. Where is gpgme used? Any "unexpected" places?
Arch Linux uses gpgme to verify downloaded packages (and optionally, package databases) for example.
PGP mail?
Which almost no one uses.
Wrong bubble ;-)
If only people in a certain bubble use it, then almost no one actually uses it.
> no one actually uses it.
A lot of people use it especially certain high value targets on darknet drug markets who might miss this.
A lot of projects do still use it for signing projects though many have opted for simpler solutions (or unfortunately no signing).
I think Debian still uses it (not sure about ubuntu) in apt.
Darknet drug dealers are still an extreme minority of people. You still have not negated my statement.
Sure, GPG gets used for signing packages and that COULD potentially lead to a supply chain attack IF this is not quickly patched.
The vulnerability is in GpgME (the library), not GnuTLS (the library).
Editorialized submission title to be better bait.
The correct title is: GnuPG Security Advisory for GPGME
Which wouldn't tell us anything before checking the link
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.
Alright, possible RCE would be fair
so essentially look at the key before? (and hope your program does not have another RCE...)
Luckily nobody uses it!
more or less than 0 impacted systems?
This is a reminder that Seqouia-PGP exists, and its 'sq' CLI is way more intuitive.