Trivy supply chain compromise via malicious release and retagged GitHub Actions
CVE-2026-33634 tracks a software supply chain compromise affecting Aqua Security's Trivy ecosystem. On 2026-03-19, a threat actor using compromised credentials published a malicious Trivy v0.69.4 release and force-pushed mutable version tags in the official GitHub Actions repositories aquasecurity/trivy-action and aquasecurity/setup-trivy so that workflows resolving those tags executed attacker-controlled code. The affected components were the aquasecurity/trivy Go binary and container image version 0.69.4, aquasecurity/trivy-action versions 0.0.1 through 0.34.2 for 76 of 77 tags, and aquasecurity/setup-trivy versions 0.2.0 through 0.2.6 prior to recreation of 0.2.6 with a safe commit. The incident was described as a continuation of an earlier late-February 2026 compromise in which credential rotation after disclosure was not atomic, potentially allowing the attacker to retain access during the rotation window and reuse valid tokens. The malicious artifacts and retagged actions were used to deliver credential-stealing malware in CI/CD environments.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
tpcp-docs, whose presence may indicate the fallback exfiltration mechanism was triggered and secrets were stolen. More broadly, ensure credential rotation is atomic during incident response so attackers cannot retain access through partially revoked tokens.Remediation
Patch, then assume compromise.
aquasecurity/trivy-action version 0.35.0, and aquasecurity/setup-trivy version 0.2.6 after it was recreated with a safe commit. Remove any affected artifacts immediately and verify whether Trivy v0.69.4 was pulled or executed from any source. Review all workflows using aquasecurity/trivy-action or aquasecurity/setup-trivy, especially those that referenced version tags rather than immutable commit SHAs. If any compromised version may have run, rotate all secrets accessible to affected pipelines immediately.Exploits
No valid public exploits. Mallory filtered out 4 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
92 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability tracked in CISA KEV and associated in this reporting with the broader TeamPCP campaign context; the content does not describe the technical flaw itself.
A specific vulnerability tracked in CISA KEV and associated in this report with the broader TeamPCP campaign context, but the content does not describe the technical nature of the flaw.
A specific vulnerability tracked in CISA KEV and associated in this reporting with the broader TeamPCP campaign context; the content does not describe the technical flaw itself.
A supply chain compromise of Aqua Security's official Trivy distribution infrastructure that weaponized Trivy artifacts and enabled large-scale theft of CI/CD runner secrets and downstream credential compromise.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.