Severity by source
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Amber
Unauthenticated attacker submits untrusted content processed by CI (AV:N/PR:N/UI:N), but requires the vulnerable headless auto-trust configuration (AC:H); full RCE on the runner gives C/I/A:H.
Primary rating from Vendor (GoogleCloud).
CVSS VectorVendor: GoogleCloud
Lifecycle Timeline
6DescriptionCVE.org
A vulnerability in the Gemini CLI and associated GitHub Action allowed an unprivileged attacker to achieve an arbitrary code execution in Gemini CLI via untrusted local .env files overriding GEMINI_CLI_HOME.
AnalysisAI
Arbitrary code execution in Google Cloud's Gemini CLI (npm @google/gemini-cli < 0.39.1) and the run-gemini-cli GitHub Action (< 0.1.22) lets an unprivileged attacker run code on the host by planting untrusted local .env / .gemini configuration files that override GEMINI_CLI_HOME. In headless (CI) mode, previous versions auto-trusted workspace folders and processed their config/environment variables, so a malicious pull request or issue processed by an automated Gemini workflow could trigger RCE; a related --yolo tool-allowlist bypass compounds the risk. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires Gemini CLI (or the run-gemini-cli Action) running in headless/non-interactive mode over folder contents the attacker can influence - specifically CI/CD workflows that process untrusted input such as externally submitted pull requests or issues. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The vendor CVSS 4.0 base score is 9.2 (AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H with low subsequent-system impact), reflecting unauthenticated, no-user-interaction remote code execution but elevated attack complexity - consistent with the requirement that the target run Gemini CLI in headless mode over untrusted folder contents (e.g., CI reviewing external PRs/issues). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade to the vendor-released fixed versions: Gemini CLI (@google/gemini-cli) 0.39.1 (or 0.40.0-preview.3 for the preview channel) and the run-gemini-cli GitHub Action 0.1.22. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, audit GitHub Actions workflows and CI/CD systems for active use of @google/gemini-cli or run-gemini-cli; disable or pause these workflows pending patch deployment. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Gemini Cli
View allSame weakness CWE-20 – Improper Input Validation
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-75326
GHSA-2255-3477-vp73