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.
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.
You can find the GitLab Omnibus related patch here: https://gitlab.com/gitlab-org/omnibus-gitlab/-/commit/279ac3...
> Exploiting this bug to mount an Remote Code Execution attack (RCE) can't be ruled out.
It's still a critical bug, just would not call it a prime example of rce.
If you believe an LLM can generate an exploit for this - feel free to post one.
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?
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 specifically in 'GPGME' though, so more limited scope I think.
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.
Sure, GPG gets used for signing packages and that COULD potentially lead to a supply chain attack IF this is not quickly patched.
The correct title is: GnuPG Security Advisory for GPGME
"Probable RCE in GnuPG clients" would be appropriate.
When someone posts a Claude POC, then the situation is different.