fix: update composite action to remediate Trivy supply chain attack#126
Merged
derrix060 merged 2 commits intoNethermindEth:mainfrom Mar 24, 2026
Merged
Conversation
The March 19, 2026 Trivy supply chain attack (GHSA-69fq-xp46-6x23) force-pushed 75 of 76 tags in aquasecurity/trivy-action to credential-stealing malware. The composite action at b59fa5c2 uses trivy-action v0.34.1 (compromised). The composite action at fefef12a (March 11 Dependabot bump) uses trivy-action v0.35.0 (SHA 57a97c7e), which is the recommended safe version — protected by GitHub's immutable releases feature. Ref: GHSA-69fq-xp46-6x23
abdul-abdi
force-pushed
the
fix/trivy-supply-chain-remediation
branch
from
2fb2df7 to
30e577d
Compare
derrix060
reviewed
Mar 24, 2026
Same broken SHA — applies the same trivy-action v0.35.0 remediation to the DockerHub build workflow.
derrix060
approved these changes
Mar 24, 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
3 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.
Summary
Updates the
github-action-image-build-and-pushcomposite action reference to remediate the March 19 Trivy supply chain attack.What happened
On March 19, 2026, a threat actor force-pushed 75 of 76 tags in
aquasecurity/trivy-actionand all 7 tags inaquasecurity/setup-trivyto credential-stealing malware. The current composite action ref (b59fa5c2) usestrivy-action@e368e328(v0.34.1), which is one of the compromised versions. This causes all Docker image builds using this reusable workflow to fail when the Trivy binary cache is cold.The fix
The composite action at
fefef12a(March 11 Dependabot bump) already updated totrivy-action@57a97c7e(v0.35.0) — the recommended safe version, protected by GitHub's immutable releases feature.Verified dependency chain
trivy-action57a97c7esetup-trivye6c2c5e3fefef12aImpact
docker-build-push-jfrog.yamlwith Trivy scanning enabled are affectedyokai-dashdev image builds have been failing since March 19 (~3 weeks)Merge order
Test plan
fefef12a2baef6d339fb4b244b4cd45c40146161exists and resolvestrivy-action@57a97c7e(v0.35.0 — confirmed safe)setup-trivy@e6c2c5e3(v0.2.4 — SHA-pinned, safe)References