CVE-2026-33634 Details
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.
A supply chain vulnerability has been identified in Aqua Security's Trivy tool, specifically in version 0.69.4 of the Trivy binary and container image, as well as in the 'aquasecurity/trivy-action' and 'aquasecurity/setup-trivy' GitHub Actions. This vulnerability was introduced when a threat actor used compromised credentials to publish a malicious Trivy release, replacing legitimate version tags in the GitHub Actions with malicious commits that included credential-stealing malware. The attack exploited a window of opportunity during a credential rotation process, allowing the attacker to maintain access and execute the malicious actions. As a result, secrets from affected pipelines may have been exfiltrated and uploaded to a repository on the victim's GitHub account.
Users should immediately update to the safe versions of Trivy (v0.69.2 or v0.69.3), 'trivy-action' (v0.35.0), and 'setup-trivy' (v0.2.6). If a compromised version of Trivy was used, all pipeline secrets should be treated as exposed and rotated. Organizations should also review their GitHub Actions workflows for signs of compromise and pin GitHub Actions to full SHA references.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Mar 24, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
This CVE is in CISA's Known Exploited Vulnerabilities Catalog
Reference CISA's BOD 22-01 and Known Exploited Vulnerabilities Catalog for further guidance and requirements.
| Vulnerability Name | Date Added | Due Date | Required Action |
|---|---|---|---|
| Aquasecurity Trivy Embedded Malicious Code Vulnerability | Mar 26, 2026 | Apr 9, 2026 | Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-506 | Embedded Malicious Code | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| aquasec setup-trivy | < 0.2.6 |
CPE
Remediation
| |
| aquasec trivy | 0.69.4 |
CPE
Remediation
| |
| aquasec trivy action | < 0.35.0 |
CPE
Remediation
| |
| litellm litellm | 1.82.7 1.82.8 |
CPE
Remediation
| |
| telnyx telnyx | 4.87.1 4.87.2 |
CPE
Remediation
| |
Change History
11 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Mar 30, 2026 | Modified Analysis | [email protected] |
| Mar 30, 2026 | CVE Modified | [email protected] |
| Mar 27, 2026 | Modified Analysis | [email protected] |
| Mar 27, 2026 | CVE Modified | [email protected] |
| Mar 26, 2026 | Initial Analysis | [email protected] |
| Mar 26, 2026 | CVE Modified | CISA-ADP |
| Mar 25, 2026 | CVE Modified | [email protected] |
| Mar 25, 2026 | CVE Modified | CISA-ADP |
| Mar 23, 2026 | New CVE Received | [email protected] |