GitHub Actions SHA Pinning Does Not Establish Commit Provenance

GitHub Actions users are being warned that SHA pinning, while valuable for preventing references from changing, does not establish who authored a pinned commit or whether it belongs to the intended upstream project. The warning follows two 2026 incidents involving a technique that uses GitHub forks to make malicious code appear trustworthy.
In March 2026, attackers who hijacked Trivy, an open-source security scanner, planted malicious code that appeared to come from GitHub's official checkout tool and labelled it as a security fix. In May, the same approach affected actions-cool/issues-helper, with credentials taken from the pipelines that executed it.
Immutability is not provenance
Pinning an action to a full commit SHA makes the referenced code immutable: a moved tag cannot silently redirect a workflow to a different commit. That protection mattered during the March 2025 compromise of tj-actions/changed-files, when malicious commits were placed behind tags across more than 23,000 repositories. Workflows pinned to SHAs were unaffected.
GitHub also allows administrators to enforce SHA pinning across an organisation. However, that enforcement verifies that a reference is a 40-character SHA; it does not verify that the commit resides in the expected upstream project. A commit from a fork can therefore be pinned while still failing the more important provenance test.
The distinction leaves three areas for teams to examine: authorship of the commit, its relationship to the upstream project, and runtime behaviour. A Docker-based action may be pinned to a SHA yet build its image when it runs, bringing in dependencies that were not fixed by the workflow reference.
What workflow lockfiles change
GitHub's 2026 Actions security roadmap put deterministic dependency locking at the centre of its plans. Workflow lockfiles entered public preview on October 14 and became generally available on October 28, 2026. They record commits for actions and their transitive dependencies, so later tag changes do not alter the dependencies used by a workflow run.
The mechanism also requires locked commits to exist on a branch in the source repository, reducing exposure to fork-only impostors. GitHub states, however, that locking does not determine whether a dependency is safe. It does not answer authorship questions or address runtime image builds, and lockfiles are not currently supported on GitHub Enterprise Server. Immutable releases add another control only where maintainers choose to provide them.
Implications for CI/CD policy
The issue is the focus of the webinar GitHub Actions Security Beyond SHA Pinning, led by Erika Heidi, Staff Developer Relations Engineer at Chainguard. The session is aimed at platform and DevOps engineers, AppSec and DevSecOps teams, and security leaders responsible for CI/CD policy.
For organisations that run third-party GitHub Actions, SHA pinning should remain a baseline rather than a final approval decision. Pipeline policies need to account for the origin of each commit, the repository relationship behind the reference, and dependencies introduced during runtime builds before an action is treated as trusted.

