CVE-2026-33634: GO-2026-4919 - Trivy ecosystem supply chain was briefly compromised in github.com/aquasecurity/trivy

CVE-2026-33634 · Severity: critical · CVSS 4 · Exploited in the wild · Published 2026-04-01

Aqua Security's Trivy, a widely used tool for scanning software for security flaws, was compromised in a supply chain attack where malicious code was inserted into official releases and GitHub Actions. If used, this malicious code can steal highly sensitive information from your development environment, including cloud credentials, database passwords, and encryption keys. Organizations must immediately rotate all secrets that may have been exposed and update to verified safe versions of the software.

Technologies: Aqua Security Trivy, github.com/aquasecurity/trivy (Go). Vendors: Aqua Security, GitHub Actions, Go.

Quick answers

Is CVE-2026-33634 exploited in the wild?
Yes. CVE-2026-33634 is known to be exploited in the wild, first recorded on 26 March 2026. Treat it as urgent.
How severe is CVE-2026-33634?
Critical severity, with a CVSS score of 4, published 1 April 2026.
Which products and versions are affected?
Aqua Security Setup-Trivy 0.2.0 - 0.2.6; Aqua Security Trivy 0.69.4; Aqua Security Trivy-Action 0.0.1 - 0.34.2; aquasecurity/setup-trivy (GitHub Actions) ECOSYSTEM:introduced=0,fixed=0.2.6; and 2 more.
Is there a fix for CVE-2026-33634?
Yes. aquasecurity/setup-trivy (GitHub Actions): upgrade to 0.2.6 or later; aquasecurity/trivy-action (GitHub Actions): upgrade to 0.35.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-33634 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-33634?
Check whether you run Aqua Security Setup-Trivy, Aqua Security Trivy, Aqua Security Trivy-Action or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • aquasecurity/setup-trivy (GitHub Actions): upgrade to 0.2.6 or later
  • aquasecurity/trivy-action (GitHub Actions): upgrade to 0.35.0 or later

Technical details

This is a supply chain compromise (CWE-506) where a threat actor used compromised credentials to publish a malicious version of the Trivy binary (v0.69.4) and force-push malicious commits to existing version tags for 'trivy-action' and 'setup-trivy' GitHub Actions. The malicious code is designed to exfiltrate environment variables, SSH keys, and cloud provider tokens from the CI/CD runner to an attacker-controlled repository (often named 'tpcp-docs'). The attack was possible due to non-atomic credential rotation following a previous incident in February 2026. Users are advised to update to Trivy v0.35.0 (action) or v0.69.5+ (binary), rotate all secrets accessible to affected pipelines, and pin GitHub Actions to immutable commit SHAs rather than mutable tags.

Affected products

  • Aqua Security Trivy 0.69.4
  • Aqua Security trivy-action 0.0.1 - 0.34.2
  • Aqua Security setup-trivy 0.2.0 - 0.2.6

Identifiers

  • CVE-2026-33634
  • GHSA-69fq-xp46-6x23
  • GO-2026-4919

Timeline

  • 2026-02-01: other: Initial supply chain attack began late February 2026
  • 2026-03-01: disclosed: Initial disclosure and secret rotation attempt
  • 2026-03-19: exploited: Threat actor published malicious releases using exfiltrated credentials
  • 2026-03-26: advisory: CVE-2026-33634 published and added to CISA KEV

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.