security: digest-pin Dockerfile base images#156
Merged
cx-artur-ribeiro merged 2 commits intomasterfrom Apr 23, 2026
Merged
Conversation
|
KICS version: v2.1.19 Queries Results
|
cx-miguel-dasilva
approved these changes
Apr 23, 2026
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
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 both FROM images by SHA256 digest so a repushed/poisoned tag on the upstream registry cannot flow into the Action build. SHA-pinning the GitHub Action alone is insufficient because the Docker image tag remains mutable on Docker Hub.
I've downgraded kics to version 2.1.19 for now:
The tag is kept alongside the digest as a human-readable intent marker;
Docker resolves the pull by digest, so a mismatched tag republish fails closed instead of silently substituting content.
Thanks to @bsgrigorov and everyone involved for bringing this issue to our attention.