Trivy Supply-Chain Hijack: trivy-action Steals CI Secrets
If any pipeline ran trivy-action by tag, setup-trivy, or Trivy 0.69.4 to 0.69.6 during the March 19-23, 2026 windows, every secret that job could see is burned; if you pinned SHAs, digests or 0.69.3, you were fine.
Must act: Teams whose CI ran aquasecurity/trivy-action by tag on March 19-20, 2026, setup-trivy unpinned, Trivy 0.69.4 from any channel or Docker Hub 0.69.5/0.69.6/latest on March 22-23, or the Checkmarx actions and Open VSX extensions on March 23.
Can relax: Users who pinned the action to a commit SHA after 2025-04-09, used images by digest, installed Trivy through the official Homebrew formula, or stayed on Trivy 0.69.3 or earlier were not affected.
- Grep workflows for trivy-action and setup-trivy references and check run logs from March 19-20, 2026
- Pin actions to full commit SHAs and container images to digests
- Rotate every secret available to affected jobs: cloud keys, GitHub PATs, registry creds, SSH keys, Kubernetes tokens, .env values