Trivy ecosystem supply chain briefly compromised
Summary
| CVE | CVE-2026-33634 |
|---|---|
| State | PUBLISHED |
| Assigner | GitHub_M |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-03-23 22:16:31 UTC |
| Updated | 2026-03-30 18:50:38 UTC |
| 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. |
Risk And Classification
Primary CVSS: v4.0 9.4 CRITICAL from [email protected]
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS: 0.211530000 probability, percentile 0.956250000 (date 2026-04-01)
CISA KEV: Listed on 2026-03-26; due 2026-04-09; ransomware use Unknown
Problem Types: CWE-506 | CWE-506 CWE-506: Embedded Malicious Code
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 4.0 | [email protected] | Secondary | 9.4 | CRITICAL | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/C... |
| 4.0 | CNA | DECLARED | 9.4 | CRITICAL | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H |
| 3.1 | [email protected] | Primary | 8.8 | HIGH | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
CVSS v4.0 Breakdown
Attack Vector
NetworkAttack Complexity
LowAttack Requirements
NonePrivileges Required
LowUser Interaction
NoneConfidentiality
HighIntegrity
HighAvailability
HighSub Conf.
HighSub Integrity
HighSub Availability
HighCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA Known Exploited Vulnerability
| Vendor | Aquasecurity |
|---|---|
| Product | Trivy |
| Name | Aquasecurity Trivy Embedded Malicious Code Vulnerability |
| Required Action | Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. |
| Notes | This vulnerability involves a supply‑chain compromise in a product that may be used across multiple products and environments. Additional vendor‑provided guidance must be followed to ensure full remediation. For more information, please see: https://github.com/advisories/GHSA-69fq-xp46-6x23 ; https://nvd.nist.gov/vuln/detail/CVE-2026-33634 |
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Aquasec | Setup-trivy | All | All | All | All |
| Application | Aquasec | Trivy | 0.69.4 | All | All | All |
| Application | Aquasec | Trivy Action | All | All | All | All |
| Application | Litellm | Litellm | 1.82.7 | All | All | All |
| Application | Litellm | Litellm | 1.82.8 | All | All | All |
| Application | Telnyx | Telnyx | 4.87.1 | All | All | All |
| Application | Telnyx | Telnyx | 4.87.2 | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Aquasecurity | Setup-trivy | affected < 0.2.6 | Not specified |
| CNA | Aquasecurity | Trivy-action | affected < 0.35.0 | Not specified |
| CNA | Aquasecurity | Trivy | affected = 0.69.4 | Not specified |
| CNA | BerriAI | LiteLLM | affected >= 1.82.7, <= 1.82.8 | Not specified |
| CNA | Team-telnyx | Telnyx | affected >= 4.87.1, <= 4.87.2 | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| inspector.pypi.io/project/litellm/1.82.8/packages/f6/2c/731b614e6cee0bca1e010a3... | [email protected] | inspector.pypi.io | Broken Link |
| github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23 | [email protected] | github.com | Exploit, Mitigation, Vendor Advisory |
| github.com/BerriAI/litellm/issues/24518 | [email protected] | github.com | Issue Tracking, Mitigation, Third Party Advisory |
| rosesecurity.dev/2026/03/20/typosquatting-trivy.html | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | rosesecurity.dev | Exploit, Third Party Advisory |
| www.cisa.gov/known-exploited-vulnerabilities-catalog | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | www.cisa.gov | US Government Resource |
| github.com/aquasecurity/trivy/discussions/10425 | [email protected] | github.com | Issue Tracking, Vendor Advisory |
| github.com/pypa/advisory-database/tree/main/vulns/litellm/PYSEC-2026-2.yaml | [email protected] | github.com | Third Party Advisory |
| futuresearch.ai/blog/litellm-pypi-supply-chain-attack | [email protected] | futuresearch.ai | Third Party Advisory |
| inspector.pypi.io/project/litellm/1.82.7/packages/79/5f/b6998d42c6ccd32d36e1266... | [email protected] | inspector.pypi.io | Broken Link |
| www.wiz.io/blog/teampcp-attack-kics-github-action | [email protected] | www.wiz.io | Not Applicable |
| github.com/team-telnyx/telnyx-python/security/advisories/GHSA-955r-262c-... | [email protected] | github.com | Third Party Advisory |
| www.microsoft.com/en-us/security/blog/2026/03/24/detecting-investigating-defend... | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | www.microsoft.com | Technical Description |
| github.com/BerriAI/litellm/issues/24518 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | github.com | Issue Tracking, Mitigation, Third Party Advisory |
| docs.litellm.ai/blog/security-update-march-2026 | [email protected] | docs.litellm.ai | Third Party Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
| CISA Known Exploited Vulnerabilities catalog | CISA | www.cisa.gov | kev |
No vendor comments have been submitted for this CVE.
Additional Advisory Data
| Source | Time | Event |
|---|---|---|
| ADP | 2026-03-26T00:00:00.000Z | CVE-2026-33634 added to CISA KEV |
There are currently no legacy QID mappings associated with this CVE.