If you use Gemini CLI, watch out: Google has patched a CVSS 10.0 vulnerability in its command-line AI tool and is warning anyone running it in headless mode, or through GitHub Actions, to review their workflows. The update to Gemini CLI and the run-gemini-cli GitHub Action, published last week but largely unnoticed until one of the two credited research teams published its writeup on Wednesday, fixes a critical - and apparently easy-to-abuse - flaw tied to over-permissive workspace trust settings. Per Google's advisory published to GitHub, the issue stems from how the headless mode of Gemini CLI (frequently used in CI/CD environments and increasingly by AI agents) handles workspace folder trust: It automatically assumes any of the workspace folders it's active in are trusted for the purpose of loading configuration files and environment variables. We trust you can see the problem here. Novee researcher Elad Meged discovered the vulnerability (independently of Pillar Security's Dan Lisichkin, who Google also credited for the find), he told us, while studying CI/CD supply chain attack vectors. "This vulnerability had nothing to do with prompt injection or the model 'deciding' to act maliciously," Meged told The Register in an email. "It was an infrastructure-level issue, where attacker-controlled content was silently accepted as trusted configuration and executed before any sandbox was initialized." A CVE hasn't been issued for the issue yet, but Meged told us Google has confir...
Google's fix for critical Gemini CLI bug might break your CI/CD pipelines
The Register
·Brandon Vigliarolo
·Published Apr 30, 2026
·Updated
Affected Software
2 affected components
Google Gemini CLI<0.39.1
Google run-gemini-cli GitHub Action
Frequently Asked Questions
1
What is the main topic of this article?
The article discusses a critical vulnerability in Google's Gemini CLI tool and the implications of its recent patch.
2
What security implications are discussed in the article?
The article highlights a CVSS 10.0 vulnerability in Gemini CLI that poses risks when used in headless mode or via GitHub Actions.
3
What products or software are affected?
The affected products include Google Gemini CLI and the Google run-gemini-cli GitHub Action.
4
What should users of Gemini CLI do in response to the patch?
Users are advised to review their CI/CD workflows to mitigate potential disruptions caused by the update.
5
What are the potential consequences of not updating Gemini CLI?
Failure to update Gemini CLI could leave systems exposed to exploitation of the critical vulnerability.