The one where the solution is so painful many will ignore it:
Primary source:
Money quote:
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.
This exact issue keeps popping up in these tools! It’s almost like security is an afterthought.
2 Likes