Vulnerability in google-github-actions/run-gemini-cli (CVE-2026-12537)
Summary
Vulnerability in google-github-actions/run-gemini-cli (CVE-2026-12537). Successful exploitation can lead to full system takeover. Exploitable via run_shell_command. Mitigation: upgrade to 0.1.22 or later.
Original description
The description as published by the source.
Summary
Gemini CLI (@google/gemini-cli) and the run-gemini-cli GitHub Action are being updated to harden workspace trust and tool allowlisting, in particular when used in untrusted environments like GitHub Actions. This update introduces a breaking change to how non-interactive (headless) environments handle folder trust, which may impact existing CI/CD workflows under specific conditions.
Details
Folder Trust in Headless Mode
In previous versions, Gemini CLI running in CI environments (headless mode) automatically trusted workspace folders for the purpose of loading configuration and environment variables. This is potentially risky in situations where Gemini CLI runs on untrusted folders in headless mode (e.g. CI workflows that review user-submitted pull requests). If used with untrusted directory contents, this could lead to remote code execution via malicious environment variables in the local .gemini/ directory.
To ensure consistency and user control, the latest update aligns headless mode behavior with interactive mode, requiring folders to be explicitly trusted before configuration files (such as .env) are processed.
As a result of this change, GitHub Actions and other automated pipelines that rely on the previous automatic trust behavior will fail to load workspace-specific settings until they are updated to use explicit trust mechanisms.
Tool Allowlisting under --yolo
In previous versions, when Gemini CLI was configured to run in --yolo mode, it…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-12537 has been found in google-github-actions/run-gemini-cli.
Attackers can target a specific entry point like run_shell_command over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade google-github-actions/run-gemini-cli to 0.1.22 or later.
If unsure, ask your IT team or search "google-github-actions/run-gemini-cli CVE-2026-12537" on the vendor's site.
CVE-2026-12537 (google-github-actions/run-gemini-cli) — CWE-20 / CVSS v3 7.8
Attack vector: local / unauthenticated
Attack surface: run_shell_command
Patched: 0.1.22 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in google-github-actions/run-gemini-cli. Attackers reach the vulnerable code path via run_shell_command without authentication.
Check the vendor advisory for the affected versions of google-github-actions/run-gemini-cli. Attack surface: run_shell_command.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 0.1.22.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'google-github-actions/run-gemini-cli' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'google-github-actions/run-gemini-cli' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
google-github-actions/run-gemini-cliを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade google-github-actions/run-gemini-cli to 0.1.22ステージング環境で 0.1.22 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com