# CVE-2026-33634: Aquasecurity Trivy Embedded Malicious Code > Attackers compromised Trivy releases and GitHub Actions to steal credentials and execute malicious code, requiring immediate secret rotation and artifact removal. - **Severity:** Critical 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`) - **Exploited in the wild:** Yes, since 26 Mar 2026 (CISA KEV) - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Mar 2026 - **Updated:** 30 Mar 2026 - **Also known as:** GHSA-69fq-xp46-6x23, GO-2026-4919, MINI-525v-fp37-6mfg, MINI-8j9g-3jx2-jqhq, MINI-c3rh-pv45-8wrw, MINI-gvrh-wv5j-w3mf, MINI-jhgm-4fx6-g8q5, MINI-v7fw-qx6p-4c94, MINI-vmv5-jqq6-89j2 ## What is CVE-2026-33634? CVE-2026-33634 is a critical vulnerability in BerriAI LiteLLM, published on 23 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-506 (Embedded Malicious Code) ## Which versions are affected by CVE-2026-33634? 5 open source packages ship an affected version, including github.com/aquasecurity/trivy, aquasecurity/setup-trivy and aquasecurity/trivy-action. It affects 5 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/aquasecurity/trivy` | Go | All versions | None | | `github.com/aquasecurity/trivy` | Go | All versions | None | | `github.com/aquasecurity/trivy` | Go | From 0.69.4 | None | | `aquasecurity/setup-trivy` | GitHub Actions | All versions | 0.2.6 | | `aquasecurity/trivy-action` | GitHub Actions | All versions | 0.35.0 | Products: Aquasec Setup-Trivy, Aquasec Trivy, Aquasec Trivy Action, Litellm Litellm, Telnyx Telnyx. ## How do I fix CVE-2026-33634? Upgrade to a fixed version. US federal agencies must fix it by 9 Apr 2026. ## Is CVE-2026-33634 being exploited? Yes. Attackers have exploited CVE-2026-33634 in the wild since at least 26 Mar 2026. Public exploit code: - CVE-2026-33634 (CVSS 9.4) — The most impactful CI/CD supply chain attack of 2026 so far. (github_poc): https://github.com/ugurrates/teampcp-supply-chain-attack - Scanner de IOCs del ataque de cadena de suministro TeamPCP (CVE-2026-33634). (github_poc): https://github.com/fevar54/CVE-2026-33634-Scanner - Companion source for YouTube video "Stop Mounting docker.sock — Run Trivy Without Giving Away Root Access — (inspired by CVE-2026-33634)" (github_poc): https://github.com/AshleyT3/docker-socket-risk-demos - Formally verified, quantitative reconstruction of the Trivy/TeamPCP GitHub Actions supply-chain attack (CVE-2026-33634): a TLA+/TLC incident model, PRISM probabilistic analysis, and a 189-workflow corpus study. (github_poc): https://github.com/dfs333/trivysupplychainanalysis - https://github.com/joaovicdev/EXPLOIT-CVE-2026-33634 (github_poc): https://github.com/joaovicdev/EXPLOIT-CVE-2026-33634 ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-33634 and fix it if it is affected. What it is: CVE-2026-33634 is a critical vulnerability in BerriAI LiteLLM, published on 23 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: Yes. Attackers have exploited CVE-2026-33634 in the wild since at least 26 Mar 2026. Affected packages and fixed versions: - github.com/aquasecurity/trivy (Go): affected all versions; no fix listed - github.com/aquasecurity/trivy (Go): affected all versions; no fix listed - github.com/aquasecurity/trivy (Go): affected from 0.69.4; no fix listed - aquasecurity/setup-trivy (GitHub Actions): affected all versions; fixed in 0.2.6 - aquasecurity/trivy-action (GitHub Actions): affected all versions; fixed in 0.35.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-33634/ (Markdown: https://insights.sbomify.com/CVE-2026-33634/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33634 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33634 - OSV: https://osv.dev/vulnerability/CVE-2026-33634 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-33634/ Summaries are generated and may contain mistakes; the official description above is the record.