← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Attackers Bypass GitHub SHA Pinning Using Forked Repositories

🔄 Updated 4d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • SHA pinning prevents code changes but not malicious code from forks.
  • Trivy and actions-cool/issues-helper were compromised using this method.
  • GitHub's workflow lockfiles address some issues but not all.
  • Pinning does not verify authorship or project membership of commits.

SHA Pinning Vulnerability Discovered

GitHub's SHA pinning, a common defense against software supply chain attacks, has been circumvented by attackers. This method involves planting malicious code in project forks that appears to originate from official tools, even when pinned to a specific SHA. The core issue is that pinning ensures the code remains unchanged, but it does not verify the author or the original source of the commit.

Real-World Exploitations

In March 2026, hackers compromised Trivy, an open-source security scanner, by introducing malicious code disguised as a security fix from GitHub's checkout tool. This code would have passed checks even for teams using SHA pinning. A similar attack occurred in May against the actions-cool/issues-helper tool, resulting in credential theft from affected pipelines.

Limitations of SHA Pinning

While SHA pinning prevents tags from being repointed to malicious commits, as seen in the March 2025 tj-actions/changed-files compromise, it leaves critical security questions unanswered. A pinned SHA does not confirm who wrote the commit, nor does it verify that the commit belongs to the upstream project. Furthermore, Docker-based actions can still pull in un-frozen dependencies at runtime, even when pinned.

GitHub's Lockfiles Offer Partial Solution

GitHub introduced workflow lockfiles, generally available since October 28, 2026, as part of its 2026 Actions security roadmap. These lockfiles tie runs to recorded commits for actions and their transitive dependencies, requiring locked commits to exist on a branch of the source repository. This feature helps mitigate fork-only impostors, but GitHub's documentation indicates it does not fully determine the trustworthiness of the code.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Attackers have found a method to bypass GitHub SHA pinning by using malicious code from project forks, as demonstrated in incidents involving Trivy and actions-cool/issues-helper. This technique exploits the fact that SHA pinning guarantees code immutability but not its authorship or origin within the upstream project. The issue highlights a gap in current supply chain security practices for GitHub Actions.