GitHub Actions pinning to exact commit SHAs has become the standard defense against software supply chain attacks, yet attackers have already found ways to bypass it. In March 2026, the threat actors who compromised Trivy, a widely used open-source security scanner, planted malicious code that appeared to originate from GitHub’s official checkout tool and was even labeled as a security fix. Any workflow pinned to that SHA would have passed every automated check.
The technique exploits GitHub’s repository network, which allows forks to share code with the original project. The same method was used in May against the popular actions-cool/issues-helper action, resulting in credential theft from pipelines that executed the malicious commit. The core limitation is clear: pinning guarantees the code will not change, but it does not guarantee who authored the commit or that the commit resides in the upstream repository.
Immutability Is Not Provenance
SHA pinning earned its reputation after the tj-actions/changed-files compromise in March 2025, when tags were repointed to malicious commits across more than 23,000 repositories. Teams that had pinned to SHAs remained unaffected. GitHub now allows administrators to enforce pinning organization-wide. However, a pinned SHA still leaves three critical questions unanswered:
- Authorship: A SHA does not reveal who wrote the commit; any fork commit can be pinned.
- Project membership: Org-level enforcement only verifies that a reference is a 40-character SHA, not that the commit actually exists in the upstream project.
- Runtime: Docker-based actions pinned to a SHA can still build images at runtime, pulling in unfrozen dependencies.
GitHub’s workflow lockfiles, released to general availability on 28 October 2026, tie every run to recorded commits for actions and their transitive dependencies. Locked commits must exist on a branch of the source repository, which reduces the risk of fork-only impostors. Nevertheless, the official changelog states that locking “does not determine whether the dependency itself is safe,” leaving commit authorship and runtime builds unresolved. Lockfiles are also not yet supported on GitHub Enterprise Server.
The upcoming webinar “GitHub Actions Security Beyond SHA Pinning,” led by Erika Heidi, Staff Developer Relations Engineer at Chainguard, will provide a detailed analysis of these remaining gaps and present additional mitigation strategies, including curated catalogs of vetted actions.


