Pinning specific versions of GitHub Actions using SHA codes has been a primary defense strategy against software supply chain attacks. However, recent developments have shown that this method has its vulnerabilities. Hackers have discovered techniques to bypass these defenses, posing significant risks to software integrity and security.
The Threat Unveiled: Recent Incidents
In March 2026, a major incident highlighted the limitations of SHA pinning. Hackers infiltrated Trivy, a well-known open-source security scanner, by embedding malicious code disguised as a legitimate security update from GitHub’s official tools. This trickery was achieved due to GitHub’s allowance of code sharing between forks and the original projects. A similar breach occurred in May, targeting the actions-cool/issues-helper tool, leading to unauthorized credential access.
These attacks underscore a critical flaw: while pinning ensures code consistency, it does not verify the authenticity of the code’s origin. This gap is at the heart of an upcoming webinar titled ‘GitHub Actions Security Beyond SHA Pinning,’ aimed at educating teams on the true extent of protection offered by pinning.
Understanding the Limits of Immutability
SHA pinning has earned its place in security protocols, notably during the tj-actions/changed-files incident in March 2025, where it protected numerous repositories from a widespread compromise. GitHub has since allowed organizations to enforce pinning as a policy, though the practice leaves several critical questions unanswered.
Pinning does not guarantee the author’s identity, nor does it ensure that a commit genuinely belongs to the main project. Additionally, Docker-based actions pinned to SHAs can still incorporate dependencies at runtime, which may not have been previously verified.
Advancements and Remaining Challenges
GitHub’s 2026 security roadmap introduced workflow lockfiles, which became widely available in October. These lockfiles record dependencies, adding an extra layer of security by ensuring that forks cannot impersonate the original project. However, challenges remain, as the locking mechanism does not inherently validate the safety of dependencies or address runtime build issues.
To tackle these challenges, the upcoming webinar, led by Erika Heidi from Chainguard, will delve into the distinctions between immutability and provenance. It will explore organization-level pin enforcement, the risks of impostor commits, and additional strategies to bridge the trust gap in software pipelines.
Why You Should Attend
The session is designed for platform and DevOps engineers, AppSec and DevSecOps teams, and security leaders who have previously relied on SHA pinning. Attendees will learn about new vulnerabilities and gain insights into enhancing security measures. The webinar aims to equip participants with the knowledge to protect their workflows against disguised malicious commits.
Register for ‘GitHub Actions Security Beyond SHA Pinning’ to choose a session time that suits you and uncover the hidden vulnerabilities in your security practices. Stay informed and safeguard your development processes against future threats.
