Threat Feed

CVE-2026-33634: Aquasecurity Trivy · Supply chain compromise

Exploitation: In the wild · CVSS 9.4 Critical · Authenticated · Published 2026-03-23

Description

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.

Enclave's analysis

This isn't a code bug. Attackers used stolen credentials on March 19, 2026 to push a malicious Trivy v0.69.4 and to repoint tags in the trivy-action and setup-trivy GitHub Actions. The poisoned code steals CI/CD secrets when a pipeline runs it. CISA lists it as actively exploited. If anything ran an affected version, treat every secret that pipeline could reach as stolen and rotate it. Pin Actions to full commit SHAs.

Fix

Upgrade aquasecurity/trivy-action to 0.35.0; aquasecurity/setup-trivy to 0.2.6. No fixed version is listed for setup-trivy, trivy-action, trivy and others; follow the vendor advisory.

Affected versions

ProductVulnerableFixed in
setup-trivy< 0.2.6Not listed
trivy-action< 0.35.0Not listed
trivy= 0.69.4Not listed
LiteLLM>= 1.82.7, <= 1.82.8Not listed
telnyx>= 4.87.1, <= 4.87.2Not listed
aquasecurity/trivy= 0.69.4 (0.69.2 and 0.69.3 known safe)Not listed
aquasecurity/trivy-action< 0.35.0 (tags 0.0.1 - 0.34.2, 76 of 77 tags)0.35.0
aquasecurity/setup-trivy< 0.2.6 (all 7 tags replaced before 0.2.6 was recreated with a safe commit)0.2.6
BerriAI LiteLLM>= 1.82.7, <= 1.82.8Not listed
team-telnyx telnyx>= 4.87.1, <= 4.87.2Not listed

Seen in 4 sources