ci: pin GitHub Actions to full commit SHAs - #123
Open
razorsec wants to merge 2 commits into
Open
Conversation
Floating tags like @v3/@v4/@v6 are a supply chain attack surface — a compromised upstream release can run arbitrary code in this workflow. Pin every action to its current full SHA; the version tag is kept as a comment so the intent stays readable. Actions pinned: - actions/checkout v4 - docker/setup-qemu-action v3 - docker/setup-buildx-action v3 - docker/login-action v3 - docker/metadata-action v5 - docker/build-push-action v6
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.
What
Pins all third-party GitHub Actions in
docker-publish.ymlto their full commit SHA instead of floating version tags.Why
Floating tags (
@v3,@v4,@v6) are a supply chain risk — if any upstream action repo is compromised, a malicious release can silently run in this workflow withpackages: writeaccess to GHCR. The June 2026claude-code-actionCVE used this exact vector.Pinning to SHAs means only an explicit update to this file can change what code runs. Version tags are kept as inline comments for readability.
Actions pinned
34e114876b0b11c390a56381ad16ebd13914f8d5c7c53464625b32c7a7e944ae62b3e17d2b6001308d2750c68a42422c14e847fe6c8ac0403b4cbd6fc94ce9fb468520275223c153574b00df6fe4bcc9c299e40c65443455700f0fdfc63efafe5b34905110e90e3645eae34f1e60eeb005ba3a3d33f178e8