Pinning 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.
In March 2026, the hackers who hijacked Trivy, a widely used open-source security scanner, planted malicious code that looked like it came from GitHub's official checkout tool. They even labeled it a security fix. Teams pinned to it would have passed every check.
The trick works because GitHub lets copies of a project, called forks, share code with the original. In May, the same technique hit the popular actions-cool/issues-helper tool, stealing credentials from the pipelines that ran it.
The lesson: pinning guarantees the code won't change, but not who wrote it.
That gap is the focus of an upcoming webinar, GitHub Actions Security Beyond SHA Pinning. If your team treats pinning as the finish line, save your seat to learn what it actually protects you from, and what it doesn't.
Pinning earned its reputation. When the tj-actions/changed-files compromise repointed tags to a malicious commit across more than 23,000 repositories in March 2025, teams that had pinned to SHAs were unaffected.
GitHub now lets administrators enforce pinning as an organization-wide policy, and few security teams argue against it.
With agentic development pushing more code through CI than ever, each of those gaps gets exercised more often and reviewed less closely.
GitHub's 2026 Actions security roadmap, published March 26, put deterministic dependency locking front and center. Workflow lockfiles entered public preview on October 14 and became generally available on October 28, 2026.
Source link







