Pin third-party GitHub Actions to commit SHAs#7
Merged
Conversation
Tag-pinned actions (@v4, @v2, @v0.2.19) are vulnerable to tag takeover: a maintainer or anyone who steals their token can push a new commit to the moving tag and the next workflow run executes that code with the release token. The TanStack supply-chain compromise (May 2026) exploited exactly this pattern. SHA-pinning ensures we only run the bytes we audited. The original tag is kept as a comment after each SHA for readability. dtolnay/rust-toolchain@stable is intentionally left unpinned: that action reads github.action_ref to pick which Rust toolchain to install, so SHA-pinning would break it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
release.ymlandci.ymlto a commit SHA (with the original tag kept as a trailing comment)Why
Tag-pinned actions (
@v4,@v2,@v0.2.19) are re-resolved on every run. A maintainer — or anyone who steals their token — can push a new commit to a moving tag and the next workflow run executes that code with the repo's release token.Notes
dtolnay/rust-toolchain@stableis intentionally left unpinned: that action readsgithub.action_refto pick which Rust toolchain to install, so SHA-pinning would break it.gh api repos/OWNER/REPO/commits/TAG --jq '.sha'and update.🤖 Generated with Claude Code