highSupply Chain

Snowflake GitHub Actions Workflow Injection via Crafted Issue (snowflake-connector-net)

First seen Aug 18, 2026 · Updated Aug 18, 2026

github-actionsworkflow-injectionci-cdsupply-chaincredential-theftsnowflakeagent-relevant

Researchers at Wiz disclosed a GitHub Actions workflow injection vulnerability in Snowflake's public snowflake-connector-net repository, where a maliciously crafted GitHub issue could trigger command injection in a workflow that contained internal Jira credentials. Successful exploitation could allow an attacker to exfiltrate secrets and potentially compromise the CI/CD pipeline of a widely used Snowflake connector library.

Technical Analysis

The vulnerability resided in .github/workflows/jira_issue.yml, which processed untrusted user-controlled input (GitHub issue titles/bodies) via unsanitized interpolation into shell commands (a classic GitHub Actions 'script injection' pattern using ${{ github.event.issue.title }} or similar expressions). An attacker could craft an issue containing shell metacharacters to execute arbitrary commands within the workflow's runner context, gaining access to secrets such as internal Jira API credentials stored in the repository's GitHub Actions secrets. Because snowflake-connector-net is a widely used data connector, compromise of its CI/CD pipeline could enable a supply-chain attack against downstream consumers, including organizations that use this connector to feed data into RAG pipelines, agent tool-calling frameworks, or LLM-based analytics systems, potentially poisoning packages or leaking credentials that such AI agents rely on for database access.

Affected Systems

GitHub repository snowflakedb/snowflake-connector-net; specifically the .github/workflows/jira_issue.yml GitHub Actions workflow; any CI/CD pipeline using similar unsanitized issue-title/body interpolation patterns

Indicators of Compromise

  • N/A - vulnerability disclosure, no known active exploitation indicators reported
  • Repository: github.com/snowflakedb/snowflake-connector-net
  • Workflow file: .github/workflows/jira_issue.yml

Remediation Steps

  1. 1

    Sanitize workflow inputs

    Avoid direct interpolation of untrusted GitHub event data (issue titles, bodies, PR comments) into run: shell commands; use environment variables with proper quoting instead.

  2. 2

    Restrict workflow permissions

    Apply least-privilege GITHUB_TOKEN permissions and scope secrets (e.g., Jira credentials) only to workflows that strictly require them.

  3. 3

    Rotate exposed credentials

    Rotate any Jira or other internal API credentials that may have been referenced in the vulnerable workflow.

  4. 4

    Audit CI/CD workflows

    Review all repository workflows for similar script injection patterns using tools such as GitHub's CodeQL or zizmor to detect unsafe expression interpolation.

  5. 5

    Monitor for supply-chain compromise

    Organizations consuming snowflake-connector-net should verify package integrity and monitor for anomalous updates or credentials exposure tied to this repository.

Industries Most Exposed

TechnologySoftware DevelopmentFinancial ServicesCloud ServicesData Analytics

Sources

Respond to this threat

Pro subscribers get a full AI-generated incident-response playbook for this threat — detection, containment, eradication, and recovery steps — plus an unlimited AI Threat Advisor for questions about your environment.