Loading vulnerability…
CVE-2026-33634 tracks a software supply-chain compromise affecting Aqua Security's Trivy ecosystem. On 2026-03-19, an attacker using compromised credentials published a malicious Trivy v0.69.4 release, force-pushed 76 of 77 version tags in trivy-action to malicious commits, and replaced all setup-trivy tags with malicious commits. The incident followed an earlier compromise in late February 2026 and was enabled by non-atomic credential rotation after the initial disclosure, allowing the attacker to retain or regain access during the rotation window. Affected components include the Trivy binary and container image release 0.69.4, trivy-action versions 0.0.1 through 0.34.2, and setup-trivy versions 0.2.0 through 0.2.6 prior to recreation of the safe 0.2.6 tag. The malicious artifacts functioned as trojanized trusted releases and GitHub Actions, turning normal CI/CD and security-scanning workflows into a credential-theft vector and downstream compromise mechanism.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 5 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
107 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A supply-chain compromise affecting Trivy and related GitHub Actions components, where attackers used compromised credentials to publish malicious releases and tamper with version tags, enabling downstream credential theft and further compromises including LiteLLM.
A supply-chain compromise affecting Trivy components and malicious BerriAI LiteLLM releases 1.82.7 and 1.82.8 on PyPI, enabling credential theft from installed environments.
A high-severity supply-chain compromise affecting Trivy, where a malicious v0.69.4 tag was distributed through multiple release and container registries.
A vulnerability identified as CVE-2026-33634 that TeamPCP exploited in connection with tampering Trivy GitHub Action versions, enabling malicious workflow overwrite as part of a supply-chain credential theft campaign.
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.