Researchers Hack Google’s Gemini CLI Through Prompt Injections in GitHub Actions
A security vulnerability identified as "PromptPwnd" affects AI agents integrated into GitHub Actions and GitLab CI/CD pipelines. This vulnerability enables attackers to inject malicious prompts through untrusted user inputs, such as issue titles or pull…
A security vulnerability identified as "PromptPwnd" affects AI agents integrated into GitHub Actions and GitLab CI/CD pipelines. This vulnerability enables attackers to inject malicious prompts through untrusted user inputs, such as issue titles or pull request bodies, potentially causing AI models to execute unauthorized commands that could leak secrets or alter workflows.
Several Fortune 500 companies are potentially exposed to this vulnerability, including Google's Gemini CLI repository, which was quickly patched in response to this discovery.
The vulnerability arises when repositories integrate raw user content, such as ${{ github.event.issue.body }} , directly into AI prompts for tasks such as issue triage or PR labeling. Agents like Gemini CLI, Anthropic’s Claude Code, OpenAI Codex, and GitHub AI Inference process these inputs alongside high-privilege tools, including commands that access sensitive tokens and API keys.
In a proof-of-concept, researchers demonstrated the vulnerability by submitting an issue with hidden instructions that prompted the AI model to expose sensitive tokens publicly. Google addressed this issue within four days of disclosure through its OSS Vulnerability Rewards Program.
A security vulnerability identified as "PromptPwnd" affects AI agents integrated into GitHub Actions and GitLab CI/CD pipelines.
This incident represents the first confirmed instance of prompt injection attacks compromising CI/CD pipelines. The attack surface is expanded in certain workflows that allow activation on any user's issue submission, thus increasing the risk from external threats.
To mitigate such risks, the following strategies are recommended:
Restrict AI toolsets to prevent unauthorized issue edits or shell access. Sanitize user inputs before processing them with AI tools. Validate all AI outputs as potentially untrusted code. Limit token scopes by IP using GitHub's security features.
Configurations that allow broad user access, such as Claude’s allowed_non_write_users: "" or Codex’s allow-users: "" , should be reviewed to reduce associated risks.
As AI continues to automate development workflows, the PromptPwnd vulnerability highlights the importance of auditing AI integrations to prevent unauthorized access to sensitive information.
Based on reporting by Cyber Security News.
