Stocks● Neutral
Your CI pipeline is one force-push from compromise
The LiteLLM breach showed how a single force-push to a Git tag can expose your CI secrets. SHA pinning closes the door in two hours.
Continue with
In March 2026, LiteLLM got breached through a poisoned Trivy GitHub Action. The attacker didn't publish a new malicious action under a typo-squatted name. They force-pushed malicious code to existing release tags teams were already using.
That @v1 or @v2 you pinned to? It's mutable. Anyone with write access to that repo can point it at completely different code whenever they want. No diff. No notification. No PR review.
Here's what most workflows look like:
uses: actions/checkout@v1
That @v1 feels pinned. It looks like a version. Your brain pattern-matches it to npm semver or Docker tags and moves on. Git tags are not immutable. A maintainer, or an attacker who has compromised a maintainer, could delete and recreate that tag pointing at any commit they want. Your next workflow run pulls the new code silently.
Tag pinning gives the illusion of reproducibility without actual reproducibility. You're trusting every maintainer of every action, forever, with access to your CI secrets. A single compromised token upstream means your GITHUB_TOKEN, cloud credentials, and deploy keys are exposed.
Every startup I've worked at has pinned to tags. Every template repo on GitHub has pinned to tags. Every getting-started tutorial has told you to pin to a tag. We all collectively normalized this.
GitHub themselves recommend pinning actions to full commit SHAs: