Live › vulnerability › CVE-2026-33634
Go to dashboardAquasecurity Trivy, a widely used container and CI/CD security scanner, contains embedded malicious code. An attacker who gets this build into a pipeline can read tokens, SSH keys, cloud credentials and database passwords held in CI/CD memory.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 5h before NVD. All times on this page are UTC.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Aquasecurity Trivy | vendor | – | – |
| aquasec setup-trivy | vendor | < 0.2.6 | 0.2.6 |
| aquasec trivy | vendor | = 0.69.4 | – |
| aquasec trivy action | vendor | < 0.35.0 | 0.35.0 |
| litellm | vendor | = 1.82.7 | – |
| litellm | vendor |
| = 1.82.8 |
| – |
| telnyx | vendor | = 4.87.1 | – |
| telnyx | vendor | = 4.87.2 | – |
Unknown from the sources.
Apply the mitigations in the vendor advisory, or stop using Trivy if mitigations are unavailable (per CISA KEV required action); rotate CI/CD secrets that ran Trivy while the affected build was in use.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-33634")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.