MSRXMSRXSecurity
Vulnerabilities / CVE-2026-33634

CVE-2026-33634

Published 2026-03-23 · Analyzed

CVE-2026-33634

Aquasecurity Trivy Embedded Malicious Code Vulnerability

Exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2026-03-26, with a fix-by date of 2026-04-09. Patch it first.

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

9.4 CRITICAL
CVSS 4.0 · CNA · github.com
60%
chance of exploitation in the next 30 days (EPSS; in the top 1% of all CVEs)

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.

Scores

Affected packages and fixed versions

PackageEcosystemFixed in
github.com/aquasecurity/trivyGono fix listed
aquasecurity/trivy-actionGitHub Actions0.35.0
aquasecurity/setup-trivyGitHub Actions0.2.6

Affected products

  • aquasec setup-trivy: < 0.2.6
  • aquasec trivy: 0.69.4
  • aquasec trivy action: < 0.35.0
  • litellm litellm: 1.82.7; 1.82.8
  • telnyx telnyx: 4.87.1; 4.87.2

Weakness: CWE-506

Also known as: GHSA-69fq-xp46-6x23, GO-2026-4919

14 references (advisories, patches, write-ups)

Sources: NVD, CVE.org, OSV.dev, FIRST EPSS. Missing ones did not answer or have no record yet.

Look up another CVECheck your dependenciesScan a website