CVE-2026-13745 Google Cloud CVE debrief

Who should care

Defenders responsible for managing the Gemini CLI installation and users who utilize the CLI in their workflows should be aware of this vulnerability and take necessary precautions to prevent exploitation.

Why it matters

The vulnerability in the Gemini CLI prior to version 0.39.1 allows attackers to achieve arbitrary code execution, which can lead to unauthorized access and data breaches. Defenders should prioritize verifying the integrity of the Gemini CLI installation directory and ensuring that users are aware of the risks associated with starting the CLI in untrusted directories.

• Verify the integrity of the Gemini CLI installation directory to prevent loading of malicious configuration files
• Ensure users are aware of the risks associated with starting the CLI in untrusted directories to prevent exploitation
• Update to version 0.39.1 or later to patch the vulnerability

Technical summary

The vulnerability in the Gemini CLI prior to version 0.39.1 allows attackers to achieve arbitrary code execution by tricking a victim into starting the CLI within an untrusted directory. The vulnerability is triggered via untrusted .env files overriding GEMINI_CLI_HOME to load malicious configuration files and bypass folder trust prompts. This vulnerability can lead to unauthorized access and data breaches. Defenders should prioritize verifying the integrity of the Gemini CLI installation directory and ensuring that users are aware of the risks associated with starting the CLI in untrusted directories.

Defensive priority

Defenders should prioritize verifying the integrity of the Gemini CLI installation directory and ensuring that users are aware of the risks associated with starting the CLI in untrusted directories.

Recommended defensive actions

• Verify the integrity of the Gemini CLI installation directory
• Ensure users are aware of the risks associated with starting the CLI in untrusted directories
• Update to version 0.39.1 or later
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability, but the scope of affected versions and potential impact require further verification. The source references provided offer additional context, but a more thorough analysis is needed to fully understand the vulnerability. Defenders should verify the integrity of the Gemini CLI installation directory and review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.