chore: pin GitHub Actions to commit SHAs#360
Merged
Conversation
…ger-with-metadata.yml
fspreiss
approved these changes
Apr 9, 2026
Contributor
|
Thanks, @slawomirbabicz! |
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
2 participants
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.
Pin GitHub Actions to commit SHAs
GitHub Actions referenced by tag (e.g.
actions/checkout@v4) use a mutable pointer — the tag owner can move it to a different commit at any time, including a malicious one. This is the attack vector used in the tj-actions/changed-files incident (CVE-2025-30066).Pinning to a full 40-character commit SHA makes the reference immutable. The
# tagcomment preserves human readability so reviewers can tell which version is pinned.Important: a SHA can also originate from a forked repository. A malicious actor can fork an action, push a compromised commit to the fork, and the SHA will resolve — but it won't exist in the upstream canonical repo. Each SHA in this PR was verified against the action's canonical repository (not a fork).
Changes
actions/checkout@v4->actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1ZenVoich/setup-mops@v1->ZenVoich/setup-mops@3e94e453352269b34137b5ce49f09a8df81bed7d # v1.4.1dfinity/conventional-pr-title-action@v4.0.0->dfinity/conventional-pr-title-action@41fbb167fd524835beda2b81882b7c75b1061dbc # v4.0.0actions/setup-node@v4->actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0actions/upload-pages-artifact@v3->actions/upload-pages-artifact@56afc609e74202658d3ffba0e8f6dda462b719fa # v3.0.1actions/deploy-pages@v4->actions/deploy-pages@d6db90164ac5ed86f2b6aed7e0febac5b3c0c03e # v4.0.5Files modified
.github/workflows/backend-motoko-format-check.yml.github/workflows/backend-motoko.yml.github/workflows/backend-rust-canbench.yml.github/workflows/backend-rust.yml.github/workflows/clippy.yml.github/workflows/conventional-commits.yml.github/workflows/examples-basic-bls-signing.yml.github/workflows/examples-basic-ibe.yml.github/workflows/examples-basic-timelock-ibe.yml.github/workflows/examples-encrypted-chat.yml.github/workflows/examples-encrypted-notes-dapp.yml.github/workflows/examples-password-manager-with-metadata.yml.github/workflows/examples-password-manager.yml.github/workflows/frontend.yml.github/workflows/publish-frontend-docs.yml.github/workflows/publish-frontend.ymlSecurity warnings