Reference page — cumulative record through Sunday, October 4, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.
CVE-2026-33634
aquasecurity setup-trivy — Trivy ecosystem supply chain briefly compromised
AV AC AT PR UI VC VI VA CVSS EPSS %ile KEV
N L N L N H H H 9.4 .0168 76.2 YES
AFFECTED
Product Versions Fixed
setup-trivy < 0.2.6 – —
trivy-action < 0.35.0 – —
trivy = 0.69.4 – —
LiteLLM >= 1.82.7, <= 1.82.8 – —
telnyx >= 4.87.1, <= 4.87.2 – —
TIMELINE
Mar 23 Reserved by GitHub_M
Mar 23 Published (CNA: GitHub_M)
Mar 26 Added to CISA KEV, remediation due 2026-04-09
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.
Lifecycle
Complete event history — 3 events, chronological
| Date | Event | Detail |
|---|
| March 23, 2026 | Reserved | Reserved by GitHub_M |
| March 23, 2026 | Published | Published (CNA: GitHub_M) |
| March 26, 2026 | KEV ADDED | Added to CISA KEV, remediation due 2026-04-09 |
About this page
This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2026-33634 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Sunday, October 4, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.
