Google Fixes Maximum-Severity Gemini CLI CI RCE as Cursor Flaws Enable Code Execution

· Original article ↗

Summary

Google fixed a CVSS 10.0 Gemini CLI headless/CI flaw that let malicious workspace configuration trigger host command execution. The article also details Cursor flaw CVE-2026-26268 and an unpatched extension-access issue dubbed CursorJacking.

Key points

  • A Gemini CLI flaw with a CVSS score of 10.0 let unprivileged attackers use malicious workspace configuration to trigger command execution on the host in headless/CI environments.
  • Affected versions include @google/gemini-cli before 0.39.1 and 0.40.0-preview.3, and google-github-actions/run-gemini-cli before 0.1.22; the flaw has no CVE identifier.
  • Google's update requires explicit workspace trust and evaluates tool allowlists in --yolo mode; users should review workflows, especially those processing untrusted inputs.
  • Cursor versions before 2.5 are affected by CVE-2026-26268 (CVSS 8.1), in which a malicious embedded bare Git repository and hook can execute code when an agent performs Git operations.
  • An unpatched Cursor access-control issue dubbed CursorJacking (CVSS 8.2) may let installed extensions access locally stored API keys and session tokens; users are advised to install only trusted extensions.

Article Details

Vulnerability Types
  • Remote code execution via malicious Gemini CLI configuration in headless mode
  • Arbitrary code execution via a malicious Git hook in an embedded bare repository
  • Access-control flaw allowing extensions to access locally stored credentials
Severity
CVSS 10.0 for the Gemini CLI flaw; CVSS 8.1 for CVE-2026-26268; CVSS 8.2 for CursorJacking.
Affected Versions
  • @google/gemini-cli < 0.39.1
  • @google/gemini-cli < 0.40.0-preview.3
  • google-github-actions/run-gemini-cli < 0.1.22
  • Cursor prior to 2.5
Exploitation Status
unknown
Exploit Availability
unknown
Patch Status
partial
Workarounds
  • For trusted inputs, set GEMINI_TRUST_WORKSPACE to true; for untrusted inputs, follow Google's workflow-hardening guidance.
  • Under --yolo mode, configure tool allowlists to permit only the required safe commands.
  • Limit Cursor extensions and install only trusted extensions.

MITRE ATT&CK

CVE

People

Vendors

Products

Related Articles