Skip to content
Hackers Bypass GitHub SHA Pinning, Exposing CI/CD Vulnerabilities

Hackers Bypass GitHub SHA Pinning, Exposing CI/CD Vulnerabilities

First seen 17 Nov 2026, 16:12 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 17, 2026 at 16:12 UTC
  • •SHA pinning does not verify the authorship of code, allowing malicious commits to be pinned.
  • •Recent compromises of Trivy and actions-cool/issues-helper highlight the vulnerabilities in CI/CD pipelines.
  • •GitHub's 2026 roadmap introduces workflow lockfiles, but gaps in security remain unaddressed.

In 2026, hackers exploited vulnerabilities in GitHub's SHA pinning mechanism, a common defense against software supply chain attacks. They compromised Trivy, an open-source security scanner, and the actions-cool/issues-helper tool, allowing malicious code to masquerade as legitimate commits. This method enables attackers to execute code that appears secure, as SHA pinning only guarantees the code's immutability, not its provenance. GitHub's recent roadmap includes workflow lockfiles to enhance security but does not fully address the issues of authorship and runtime builds. The upcoming webinar aims to educate teams on these gaps and the limitations of SHA pinning. Organizations are urged to reassess their reliance on pinning as a sole security measure.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-03-01
Trivy compromised
Hackers hijacked Trivy, injecting malicious code that appeared as a security fix, affecting numerous users.
The Hacker News
2026-05-01
actions-cool/issues-helper attack
The same technique was used to compromise actions-cool/issues-helper, stealing credentials from CI/CD pipelines.
The Hacker News
2026-10-14
Workflow lockfiles public preview
GitHub introduced workflow lockfiles in public preview to enhance security against dependency issues.
The Hacker News

More articles in this cluster (3)

Common questions

What is SHA pinning?
SHA pinning is a security measure that locks a project to a specific version of code to prevent unauthorized changes.
How are organizations affected?
Organizations using SHA pinning may unknowingly run malicious code if the commit is from a compromised fork.
What should teams do to improve security?
Teams should evaluate their reliance on SHA pinning and consider implementing additional security measures like workflow lockfiles.