Snowflake GitHub Actions Repo Exposed to Command Injection via Crafted Issue Titles

Security researchers at Wiz disclosed a GitHub Actions workflow injection vulnerability in Snowflake's public snowflakedb/snowflake-connector-net repository. According to the report, the flaw resided in .github/workflows/jira_issue.yml, a workflow that ran automatically when issues were created or updated, and could reportedly be triggered by a specially crafted GitHub issue to execute arbitrary commands within the workflow's runner context — a context that had access to internal Jira credentials.

Why It Matters

Workflow injection bugs like this are a recurring class of CI/CD weakness: untrusted, attacker-controlled input (an issue title, body, or branch name) gets interpolated directly into a shell step rather than passed as a sanitized environment variable. When that happens, anyone able to open an issue on a public repository — no special access required — can potentially get code execution inside the pipeline. If the workflow holds secrets, as this one reportedly did with Jira credentials, the blast radius extends beyond the repository itself into whatever internal systems those credentials touch.

This is relevant to any organization running public repositories with issue-triggered or PR-triggered GitHub Actions workflows, particularly those that automate ticketing, notifications, or other internal integrations from public-facing repo activity.

What Defenders Should Do Now

• Audit GitHub Actions workflows for any step that interpolates untrusted context values (issue titles/bodies, PR titles, branch names, commit messages) directly into run: shell blocks instead of via safely-quoted environment variables.
• Review which secrets are exposed to workflows triggered by public, low-privilege events like issues, issue_comment, or pull_request_target, and scope credentials down to the minimum needed.
• Favor pull_request over pull_request_target where possible, and pin third-party actions to commit SHAs rather than mutable tags.
• Hunt for anomalous workflow runs tied to newly created or edited issues on public repos, especially runs that spawn unexpected shell processes or make outbound network calls to unfamiliar hosts.
• Rotate any credentials that were exposed to a vulnerable workflow, even if exploitation isn't confirmed.

This is developing intel based on a single vendor disclosure and details may evolve as more information becomes available. For the full technical writeup, see the original report from The Hacker News: Snowflake GitHub Actions Flaw Lets Crafted Issues Trigger Command Injection.