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?
You can find the GitLab Omnibus related patch here: https://gitlab.com/gitlab-org/omnibus-gitlab/-/commit/279ac3...
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 correct title is: GnuPG Security Advisory for GPGME
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?
It's specifically in 'GPGME' though, so more limited scope I think.