U.S. CISA Adds an Aquasecurity Trivy Flaw to Its Known Exploited Vulnerabilities Catalog

U.S. CISA Adds an Aquasecurity Trivy Flaw to Its Known Exploited Vulnerabilities Catalog

Security Affairs
Security AffairsMar 27, 2026

Key Takeaways

  • CISA adds Trivy CVE-2026-33634 to KEV catalog
  • Vulnerability scores 9.3, classified as critical
  • Attackers released malicious Trivy v0.69.4 via compromised credentials
  • Federal agencies must remediate by April 9, 2026
  • Pin GitHub Actions to immutable hashes, not tags

Pulse Analysis

Supply‑chain attacks have become a cornerstone of modern cyber threats, and the recent compromise of Aquasecurity's Trivy scanner illustrates why. Trivy, a popular open‑source tool for scanning container images, was hijacked when threat actors obtained credentials and pushed a malicious 0.69.4 binary to public repositories. By manipulating GitHub Actions tied to the tool, they turned routine CI/CD pipelines into data‑exfiltration vectors, exposing any environment that executed the tainted version. This incident follows a wave of attacks on software‑bill of materials (SBOM) generators, highlighting the fragility of trust in open‑source ecosystems.

CISA’s decision to list CVE-2026-33634 in its KEV catalog signals heightened federal scrutiny of supply‑chain vulnerabilities. Under Binding Operational Directive 22‑01, federal agencies are required to address cataloged flaws by a set deadline—in this case, April 9, 2026. The directive aims to reduce the attack surface across the federal civilian executive branch (FCEB) by enforcing systematic patching and secret rotation. Private sector entities, while not bound by the directive, are urged to follow the same remediation timeline to avoid cascading risks, especially given the shared use of Trivy in DevOps pipelines.

Mitigation begins with immediate removal of compromised Trivy binaries, container images, and any affected GitHub Actions. Organizations should rotate all secrets that may have been exposed and audit logs for anomalous activity around the March 19‑20 window. Best practices now emphasize pinning CI/CD actions to immutable commit hashes rather than mutable version tags, a simple change that can thwart future tampering. As supply‑chain threats evolve, continuous monitoring of CISA’s KEV catalog and proactive secret management will be essential components of a resilient cybersecurity posture.

U.S. CISA adds an Aquasecurity Trivy flaw to its Known Exploited Vulnerabilities catalog

Comments

Want to join the conversation?