Aquasecurity · Trivy · CWE-506 · published 2026-03-23
CVE-2026-33634Aquasecurity Trivy Embedded Malicious Code Vulnerability
This week Known exploited in the wild.
CVE-2026-33634 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2026-03-26. EPSS estimates a 62% chance of exploitation in the next 30 days, higher than 99% of all CVEs. This Trivy vulnerability: CVSS 9.4 (v4.0), a successful attack gives total control of the component. CISA’s 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. US federal agencies must remediate by 2026-04-09. Patch this week.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
CISA 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. (federal due date 2026-04-09)
Patch events
Security softwareAquasecurity Trivy
Embedded Malicious CodeCVE-2026-33634
Why: Known exploited in the wild.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2026-03-26 | CISA KEV |
| Ransomware use | Unknown | CISA KEV |
| EPSS (30-day exploitation probability) | 62% (99th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.4 (v4.0)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 | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-506: Embedded Malicious Code
More from this vendor: all Aquasecurity vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- aquasecurity setup-trivy
< 0.2.6(affected)
- aquasecurity trivy-action
< 0.35.0(affected)
- aquasecurity trivy
= 0.69.4(affected)
- BerriAI LiteLLM
>= 1.82.7, <= 1.82.8(affected)
- team-telnyx telnyx
>= 4.87.1, <= 4.87.2(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.