CVEs / CVE-2026-33634

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

• Known exploited in the CISA KEV catalog since 26 Mar 2026
• high 8.8 CVSS 3.1 (NVD)
• EPSS 59.7% chance of exploitation in the next 30 days, higher than 99% of CVEs (30 Oct 2026)
• Last changed at its sources 28 Oct 2026

Summary

Aquasecurity Trivy contains an embedded malicious code vulnerability that could allow an attacker to gain access to everything in the CI/CD environment, including all tokens, SSH keys, cloud credentials, database passwords, and any sensitive configuration in memory.

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.

Affected and fixed versions

Package versions from GHSA-69fq-xp46-6x23, GHSA-955r-262c-33jc.

Exploitation

Severity

References

• CVE-2026-33634 on NVD
• CVE-2026-33634 in the CISA KEV catalog
• https://github.com/advisories/GHSA-69fq-xp46-6x23 (cited by CISA)
• CVE-2026-33634 on OSV
• https://docs.litellm.ai/blog/security-update-march-2026 Third Party Advisory
• https://futuresearch.ai/blog/litellm-pypi-supply-chain-attack Third Party Advisory
• https://github.com/BerriAI/litellm/issues/24518 Issue Tracking, Mitigation, Third Party Advisory
• https://github.com/aquasecurity/trivy/discussions/10425 Issue Tracking, Vendor Advisory
• https://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23 Exploit, Mitigation, Vendor Advisory
• https://github.com/pypa/advisory-database/tree/main/vulns/litellm/PYSEC-2026-2.yaml Third Party Advisory
• https://github.com/team-telnyx/telnyx-python/security/advisories/GHSA-955r-262c-33jc Third Party Advisory
• 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 Broken Link
• 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 Broken Link
• https://www.wiz.io/blog/teampcp-attack-kics-github-action Not Applicable
• https://github.com/BerriAI/litellm/issues/24518#issuecomment-4127436387 Issue Tracking, Mitigation, Third Party Advisory
• https://rosesecurity.dev/2026/03/20/typosquatting-trivy.html Exploit, Third Party Advisory
• https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-33634 US Government Resource
• https://www.microsoft.com/en-us/security/blog/2026/03/24/detecting-investigating-defending-against-trivy-supply-chain-compromise/ Technical Description