CVE-2026-33634

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-33634 is a supply chain compromise affecting Trivy, an open-source security scanner, stemming from a threat actor's use of compromised credentials to publish a malicious Trivy version 0.69.4 release on March 19, 2026. The attack also involved force-pushing 76 of 77 version tags in the aquasecurity/trivy-action GitHub Action (versions 0.0.1 through 0.34.2) to credential-stealing malware and replacing all 7 tags in the aquasecurity/setup-trivy GitHub Action (versions 0.2.0 through 0.2.6, prior to recreation of 0.2.6 with a safe commit). This incident continues a supply chain attack that began in late February 2026, exacerbated by non-atomic credential rotation after an initial March 1 disclosure, allowing the attacker to exfiltrate newly rotated secrets. Affected components include the aquasecurity/trivy Go binary and container image at version 0.69.4.

Users integrating the affected Trivy components into CI/CD pipelines, particularly those referencing version tags rather than commit SHAs in GitHub Actions workflows, could unwittingly execute the credential-stealing malware. An attacker with low-privilege access (PR:L) could exploit this over the network (AV:N) with low complexity (AC:L) and no user interaction (UI:N), achieving high confidentiality, integrity, and availability impacts (CVSS 8.8). Exploitation enables theft of secrets accessible to the compromised pipelines, with a fallback exfiltration mechanism potentially creating a repository named tpcp-docs in the victim's GitHub organization as an indicator of successful compromise.

Advisories recommend immediate rotation of all secrets accessible to affected pipelines if there's any chance a compromised version was pulled or executed, removal of affected artifacts, and review of workflows using aquasecurity/trivy-action or aquasecurity/setup-trivy. Organizations should verify whether Trivy v0.69.4 was obtained from any source, check workflow run logs from March 19–20, 2026 for signs of compromise if version tags were used, and pin GitHub Actions to full, immutable commit SHA hashes instead of mutable tags. Known safe versions include Trivy 0.69.2 and 0.69.3, trivy-action 0.35.0, and setup-trivy 0.2.6 (recreated).

This vulnerability saw real-world exploitation on March 19, 2026, as part of an ongoing supply chain campaign, with detailed discussions available in Aquasecurity's GitHub advisories and related security notices.