google-github-actions / google-github-actions/run-gemini-cli
Security: .github/commands/ TOML templates use unsafe !{echo $VAR} shell execution (incomplete PR #511 migration)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.1k
- Forks
- 285
- Avg merge
- 8h 8m
- Merged PRs (30d)
- 1
Description
The shipped .github/commands/ TOML templates still use !{echo $VAR} shell-execution syntax. PR #511 migrated examples/workflows/ to @{file} but missed these shipped templates.
Impact: Any public issue author can trigger bash pathname expansion and prompt injection on every repo using run-gemini-cli.
Fix: Submitted PR with migration to @{.gemini/context/VAR.txt}.
Ref: GHSA-62f2-6rx8-v262
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the shipped .github/commands/ TOML templates and compare them with the migrated examples/workflows/ templates from PR #511. Verify that each unsafe !{echo $VAR} usage is replaced with the referenced @{.gemini/context/VAR.txt} form, then confirm no such shell-execution syntax remains in the shipped templates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, github-actions
- Domain
- ci-cd, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100