RC RANDOM CHAOS

GitHub Actions SHA Pinning Leaves Critical Security Gaps

· via The Hacker News

Original source

Hackers Found a Way Around GitHub SHA Pinning. This Webinar Explains How to Close the Gap

The Hacker News →

Attackers have discovered methods to bypass SHA pinning, the standard defense for GitHub Actions supply chain attacks. In March 2026, Trivy, a widely used open-source security scanner, was hijacked with malicious code disguised as a security fix. GitHub’s fork architecture enables these attacks by allowing project copies to share code with originals, letting attackers create convincing impostor commits. This same technique compromised actions-cool/issues-helper in May, stealing credentials from pipelines. An earlier attack on tj-actions/changed-files in March 2025 affected more than 23,000 repositories, though teams pinned to specific SHAs were unaffected.

The fundamental flaw is that SHA pinning ensures code immutability without verifying authorship or project origin. Organization-level enforcement policies verify commits are 40-character SHAs but cannot confirm they come from the upstream repository. Docker-based actions can also build images at runtime and pull dependencies that were never frozen. These gaps expose systems to malicious commits that pass pinning checks.

GitHub introduced workflow lockfiles to address some gaps, entering public preview October 14, 2026 and becoming generally available October 28, 2026. Lockfiles tie every run to recorded commits for actions and transitive dependencies, requiring those commits to exist on source repository branches—effectively blunting fork-only impostor attacks. However, lockfiles cannot assess whether dependencies are safe, authorship verification remains unaddressed, and they’re not yet supported on GitHub Enterprise Server.

Read the full article

Continue reading at The Hacker News →

This is an AI-generated summary. Read the original for the full story.