The Hacker News
Hackers Bypass GitHub SHA Pinning in Supply Chain Attacks
Hackers have demonstrated a bypass of GitHub SHA pinning in a growing class of software supply chain attacks, The Hacker News reports. In March 2026, attackers compromised the Trivy open‑source security scanner by injecting code that appeared to come from GitHub’s official checkout tool, even labelling it as a security fix. The same approach resurfaced in May against the actions-cool/issues-helper workflow, enabling credential theft in pipelines that pinned to specific SHAs.
The publication notes that while SHA pinning prevents code from changing, it does not guarantee the author of the change, creating a provenance gap that attackers can exploit via forks and impostor commits.
The piece explains that GitHub has begun offering organisation‑wide pinning enforcement and highlights remaining gaps: authorship of a commit does not reveal who wrote it, project membership checks may not guarantee the upstream source, and runtime builds can fetch unfrozen dependencies even when a SHA is pinned.
It also describes GitHub’s 2026 Actions security roadmap and the public preview of workflow and dependency lockfiles (released 28 October 2026), which help tie runs to recorded commits but do not fully address trust in the provenance or the safety of the dependencies themselves. The Hacker News quotes that while lockfiles blunt fork‑only impostors, lockfiles are not yet fully standalone, and certain protections require maintainer opt‑in, with some gaps persisting for GitHub Enterprise Server.
The article promotes an upcoming webinar, “GitHub Actions Security Beyond SHA Pinning,” led by Erika Heidi of Chainguard, to delineate what pinning does and does not secure.