Skip to main content

Run Gemini Cli Github Action

2 CVEs product

Monthly

CVE-2026-13745 Sep 10, 08:33 CRITICAL PATCH Act Now

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. Patched by vendor; no public exploit identified at time of analysis and it is not in CISA KEV.

RCE Google Gemini Cli Run Gemini Cli Github Action Google Cloud
NVD GitHub
CVSS 4.0
9.2
EPSS
0.3%
CVE-2026-12537 Jun 24, 13:37 npm CRITICAL POC PATCH Act Now

Pre-sandbox host-level code execution in Google Gemini CLI (versions prior to 0.39.1) and the run-gemini-cli GitHub Action (prior to 0.1.22) allows an unprivileged attacker to run arbitrary commands on CI/CD runner hosts by planting a malicious .gemini/.env file in an untrusted workspace. In headless mode the tool automatically trusted workspace folders and loaded their environment variables before sandboxing, so a workflow that processes attacker-controlled content (for example reviewing a submitted pull request) would execute attacker-supplied commands on the host. No public exploit has been identified at time of analysis, but Google rates this CVSS 4.0 10.0 and a vendor advisory (GHSA-wpqr-6v78-jr5g) with fixed releases is available.

RCE Google Command Injection Gemini Cli Run Gemini Cli Github Action +1
NVD GitHub VulDB
CVSS 4.0
10.0
EPSS
0.3%
EPSS 0% CVSS 9.2
CRITICAL PATCH Act Now

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. Patched by vendor; no public exploit identified at time of analysis and it is not in CISA KEV.

RCE Google Gemini Cli +2
NVD GitHub
EPSS 0% CVSS 10.0
CRITICAL POC PATCH Act Now

Pre-sandbox host-level code execution in Google Gemini CLI (versions prior to 0.39.1) and the run-gemini-cli GitHub Action (prior to 0.1.22) allows an unprivileged attacker to run arbitrary commands on CI/CD runner hosts by planting a malicious .gemini/.env file in an untrusted workspace. In headless mode the tool automatically trusted workspace folders and loaded their environment variables before sandboxing, so a workflow that processes attacker-controlled content (for example reviewing a submitted pull request) would execute attacker-supplied commands on the host. No public exploit has been identified at time of analysis, but Google rates this CVSS 4.0 10.0 and a vendor advisory (GHSA-wpqr-6v78-jr5g) with fixed releases is available.

RCE Google Command Injection +3
NVD GitHub VulDB

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy