Snowflake GitHub Actions Flaw Allowed Command Injection via Crafted Issues

Vulnerability Discovery

Cybersecurity researchers at Wiz identified a GitHub Actions workflow injection vulnerability within Snowflake's public snowflakedb/snowflake-connector-net repository. The flaw, located in the .github/workflows/jira_issue.yml file, could be triggered by a specially crafted GitHub issue. This allowed for command execution within a workflow that exposed sensitive internal Jira credentials.

Technical Details of the Flaw

The vulnerability stemmed from the workflow directly inserting attacker-controlled issue title and body values into a shell run: block. Additionally, the workflow incorrectly checked for github.event.pull_request.user.login on an issue event, which evaluated to an empty string and bypassed a comparison intended to prevent ordinary issues from reaching the job. The exposed credentials included JIRA_BASE_URL, JIRA_USER_EMAIL, and JIRA_API_TOKEN.

Exploitation and Impact

Wiz's Red Agent system successfully exploited the injection during authorized security testing, obtaining an out-of-band callback and the Jira API token. This token, belonging to qa@snowflake.net, provided read access to Jira projects covering engineering, security compliance, and bug bounty tracking on snowflakecomputing.atlassian.net. The vulnerability was confined to the repository's CI/CD automation and did not affect any released versions of the Snowflake Connector for .NET.

Remediation and Response

Wiz reported the issue to Snowflake via HackerOne on June 23, 2026. Snowflake promptly merged a fix the same day in pull request #1402, replacing direct GitHub expression expansion with environment variables passed to jq as arguments. The vulnerable workflow had been present in the default branch for five days prior to the fix. Snowflake stated that their investigation found no evidence of unauthorized access, and the Jira token was rotated on June 24, with no unrelated external use detected during the exposure window.