CVE-2026-33634
Trivy ecosystem supply chain briefly compromised
Description
Trivy is a security scanner. On March 19, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.4 release, force-push 76 of 77 version tags in `aquasecurity/trivy-action` to credential-stealing malware, and replace all 7 tags in `aquasecurity/setup-trivy` with malicious commits. This incident is a continuation of the supply chain attack that began in late February 2026. Following the initial disclosure on March 1, credential rotation was performed but was not atomic (not all credentials were revoked simultaneously). The attacker could have use a valid token to exfiltrate newly rotated secrets during the rotation window (which lasted a few days). This could have allowed the attacker to retain access and execute the March 19 attack. Affected components include the `aquasecurity/trivy` Go / Container image version 0.69.4, the `aquasecurity/trivy-action` GitHub Action versions 0.0.1 – 0.34.2 (76/77), and the`aquasecurity/setup-trivy` GitHub Action versions 0.2.0 – 0.2.6, prior to the recreation of 0.2.6 with a safe commit. Known safe versions include versions 0.69.2 and 0.69.3 of the Trivy binary, version 0.35.0 of trivy-action, and version 0.2.6 of setup-trivy. Additionally, take other mitigations to ensure the safety of secrets. If there is any possibility that a compromised version ran in one's environment, all secrets accessible to affected pipelines must be treated as exposed and rotated immediately. Check whether one's organization pulled or executed Trivy v0.69.4 from any source. Remove any affected artifacts immediately. Review all workflows using `aquasecurity/trivy-action` or `aquasecurity/setup-trivy`. Those who referenced a version tag rather than a full commit SHA should check workflow run logs from March 19–20, 2026 for signs of compromise. Look for repositories named `tpcp-docs` in one's GitHub organization. The presence of such a repository may indicate that the fallback exfiltration mechanism was triggered and secrets were successfully stolen. Pin GitHub Actions to full, immutable commit SHA hashes, don't use mutable version tags.
In plain language
AI Act nowTrivy’s update mechanism was briefly compromised, so some common security-scanner versions could have been turned into credential-stealers; if you used those specific versions (especially in GitHub Actions/CI), you should act now.
CVE-2026-33634 is a supply-chain compromise (CWE-506) where attackers gained unauthorized access to Trivy’s infrastructure and published malicious Trivy ecosystem updates through GitHub Actions and container image releases, enabling credential theft from CI/CD environments running affected versions.
What to do now
- Check whether your CI/CD workflows or scripts used the affected versions:
trivyv0.69.4,trivy-action0.0.1–0.34.2, orsetup-trivy0.2.0–0.2.6 (especially if you used version tags rather than full commit SHAs). - If you used any of those versions, immediately rotate credentials that were available to those pipelines (API keys, registry tokens, cloud credentials, and any CI secrets) because they must be treated as exposed.
- Update to the fixed versions:
setup-trivy0.2.6,trivy action0.35.0, and avoid using the affectedtrivyv0.69.4 (use the known safe 0.69.2/0.69.3). - Re-check recent pipeline runs around 2026-03-19 to 2026-03-20 for signs of compromise, and remove any suspect build artifacts that may contain tampered scanner outputs.
- Review your workflows to pin GitHub Actions to immutable commit SHAs (not mutable version tags) for any Trivy-related actions you use.
CVSS Vector Breakdown
AV:NAttack VectorAC:LAttack ComplexityPR:LPrivileges RequiredUI:NUser InteractionS:UScopeC:HConfidentialityI:HIntegrityA:HAvailabilityWeaknesses
Affected Products
Exploitability
Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
References
Unlock Complete Vulnerability Intelligence
Get the full picture for CVE-2026-33634 and every CVE in our database. Create a free account — no credit card required.
Create Free Account