chore: update trivy to 0.74.0 in security scan workflows - #101
Merged
Conversation
the previous versions are affected by known trivy advisories (CVE-2026-54448, CVE-2026-55092, CVE-2026-63328, patched in 0.71.x/0.72.0): ecr-security-scan installed 0.69.2 via .deb and docker-security-scan used trivy-action's default 0.70.0. - ecr-security-scan: install 0.74.0 from the release tarball with sha256 verification against the release checksums file - docker-security-scan: pin trivy-action by commit sha and set an explicit trivy version instead of relying on the action default
trivy-tofu-scan.yml (2 uses, reusable with callers) and pr-checks-actions.yml (this repo's own pr secret-scan gate) were still running trivy-action's default trivy v0.70.0 via mutable tag; pinned by the same commit sha with explicit version v0.74.0
the composite installed the action by mutable tag and relied on the installer default cosign (drifts with installer releases); pinned to the v4.1.2 commit sha with cosign v3.1.3 explicit (latest stable, no known advisories)
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.
All four
trivy-actioncall sites in this repo (plus the direct install inecr-security-scan.yml) currently run Trivy versions affected by known advisories — CVE-2026-54448 (<0.71.0), CVE-2026-55092 (<0.71.1) and CVE-2026-63328 (<0.72.0):ecr-security-scan.ymlinstalled 0.69.2 via.debwith no integrity check → now installs 0.74.0 (latest stable, no known advisories) from the release tarball, verified against the releasechecksums.txtbefore use.docker-security-scan.yml(2 uses),trivy-tofu-scan.yml(2 uses) andpr-checks-actions.yml(1 use) relied ontrivy-action@v0.36.0(mutable tag) whose default bundles Trivy 0.70.0 → the action is now pinned by commit SHA everywhere and the Trivy version is set explicitly to v0.74.0.sign-imagecomposite:cosign-installerwas referenced by mutable tag and relied on the installer's default cosign — now pinned by commit SHA with cosign v3.1.3 explicit (latest stable, no known advisories).No behavior/interface changes for callers: same inputs, same outputs — only scanner/signer versions, install integrity and pinning convention.
🤖 Generated with Claude Code