---
title: "CVE-2026-33634: Aquasecurity Trivy Embedded Malicious Code Vulnerability"
url: https://erroneo.us/security/cve/CVE-2026-33634/
description: "CVE-2026-33634 (Aquasecurity Trivy): Exploited in the wild (CISA KEV). Trivy is a security scanner. On March 19, 2026, a threat actor used compromised…"
type: vulnerability-record
section: "Security Digest"
date_published: 2026-03-23
date_modified: 2026-10-21
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2026-33634"
kev: true
cvss: 9.4
epss: 0.01748
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2026-33634: Aquasecurity Trivy Embedded Malicious Code Vulnerability

**Signal:** Exploited: patch now if you run it. CISA has confirmed exploitation in the wild. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- Yes, if you run Aquasecurity Trivy. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2026-03-26, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2026-04-09 ; treat that as the outer limit, not the target.
- EPSS 1.7% , percentile 78: FIRST’s model estimates a 1.7% chance of exploitation activity in the next 30 days, higher than 78% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Needs an account (low (any account)). Exposure depends on who can log in.
- Only applies if your dependency tree includes github.com/aquasecurity/trivy (Go) = 0.69.4, no fixed version listed ; aquasecurity/trivy-action (GitHub Actions) < 0.35.0, fixed in 0.35.0 ; aquasecurity/setup-trivy (GitHub Actions) < 0.2.6, fixed in 0.2.6 . Check your lockfile, including transitive dependencies.
- Editorial verdict: Check exposure. Trivy Supply-Chain Hijack: trivy-action Steals CI Secrets — If any pipeline ran trivy-action by tag, setup-trivy, or Trivy 0.69.4 to 0.69.6 during the March 19-23, 2026 windows, every secret that job could see is burned; if you pinned SHAs, digests or 0.69.3, you were fine.

## What it is

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 theaquasecurity/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.

## Affected packages

- Go `github.com/aquasecurity/trivy` = 0.69.4 → fixed: none listed
- GitHub Actions `aquasecurity/trivy-action` < 0.35.0 → fixed: 0.35.0
- GitHub Actions `aquasecurity/setup-trivy` < 0.2.6 → fixed: 0.2.6

## Affected products (CVE record)

- aquasecurity setup-trivy: < 0.2.6
- aquasecurity trivy-action: < 0.35.0
- aquasecurity trivy: = 0.69.4
- BerriAI LiteLLM: >= 1.82.7, <= 1.82.8
- team-telnyx telnyx: >= 4.87.1, <= 4.87.2

## Severity

- GitHub_M CVSS 4.0: 9.4 `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`
- GitHub CVSS 4.0: 9.4 `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`

## Exploitation

- CISA KEV: added 2026-03-26; federal due date 2026-04-09. Known ransomware use: Unknown.
- 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.
- CISA SSVC assessment: exploitation active , automatable no , technical impact total .
- FIRST EPSS (model of 2026-10-21): 1.75% probability of exploitation activity in the next 30 days; percentile 78.

## Sources

- [GitHub Advisory GHSA-69fq-xp46-6x23](https://github.com/advisories/GHSA-69fq-xp46-6x23)
- [CVE.org record CVE-2026-33634](https://www.cve.org/CVERecord?id=CVE-2026-33634)
- [NVD entry CVE-2026-33634](https://nvd.nist.gov/vuln/detail/CVE-2026-33634)
- [CISA Known Exploited Vulnerabilities catalog entry](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-33634)
- [github.com](https://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23)
- [github.com](https://github.com/team-telnyx/telnyx-python/security/advisories/GHSA-955r-262c-33jc)
- [github.com](https://github.com/BerriAI/litellm/issues/24518)
- [docs.litellm.ai](https://docs.litellm.ai/blog/security-update-march-2026)
- [futuresearch.ai](https://futuresearch.ai/blog/litellm-pypi-supply-chain-attack)
- [github.com](https://github.com/aquasecurity/trivy/discussions/10425)
- [github.com](https://github.com/pypa/advisory-database/tree/main/vulns/litellm/PYSEC-2026-2.yaml)
- [inspector.pypi.io](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)
- [inspector.pypi.io](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)
- [wiz.io](https://www.wiz.io/blog/teampcp-attack-kics-github-action)
- [rosesecurity.dev](https://rosesecurity.dev/2026/03/20/typosquatting-trivy.html)
- [microsoft.com](https://www.microsoft.com/en-us/security/blog/2026/03/24/detecting-investigating-defending-against-trivy-supply-chain-compromise/)
- [github.com](https://github.com/BerriAI/litellm/issues/24518#issuecomment-4127436387)

---
Source page: https://erroneo.us/security/cve/CVE-2026-33634/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt