GitHub Actions SHA Pinning Cannot Verify Code Provenance, Webinar Explains

Summary
The article explains that SHA pinning makes GitHub Actions code immutable but does not verify its author. It describes fork-based attacks and says workflow lockfiles still cannot determine whether dependencies are safe.
Key points
- The article says attackers used GitHub forks to make malicious code appear to come from an official project, bypassing the assurance SHA pinning provides.
- It cites the March 2026 Trivy hijack and a May attack involving actions-cool/issues-helper, which it says stole credentials from affected pipelines.
- SHA pinning prevents code from changing but does not establish who authored it.
- GitHub Actions workflow lockfiles record commits for actions and transitive dependencies, and became generally available on October 28, 2026.
- The article says lockfiles require locked commits to exist on a branch of the source repository, but do not determine whether a dependency is safe.
- It notes that lockfiles are not currently supported on GitHub Enterprise Server and that immutable releases help only when maintainers opt in.
Article Details
- Topic
- GitHub Actions supply-chain security and the limits of SHA pinning, including how provenance and dependency lockfiles address risks from malicious commits.
People
Vendors
Products
GitHub ActionsPinning GitHub Actions to an exact version of their code, known as SHA pinning, has become the go-to defense against software supply chain attacks. Attackers have already found a way around it.GitHub Enterprise Serverreleases only help when maintainers opt in, and lockfiles aren't currently supported on GitHub Enterprise Server.
