CVE-2026-33634: Trivy ecosystem supply chain was briefly compromised
(updated )
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.
On March 22, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.5 and v0.69.6 DockerHub images.
References
- docs.litellm.ai/blog/security-update-march-2026
- futuresearch.ai/blog/litellm-pypi-supply-chain-attack
- github.com/BerriAI/litellm/issues/24518
- github.com/BerriAI/litellm/issues/24518
- github.com/advisories/GHSA-69fq-xp46-6x23
- github.com/aquasecurity/trivy
- github.com/aquasecurity/trivy/discussions/10425
- github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23
- github.com/pypa/advisory-database/tree/main/vulns/litellm/PYSEC-2026-2.yaml
- github.com/team-telnyx/telnyx-python/security/advisories/GHSA-955r-262c-33jc
- 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
- 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
- nvd.nist.gov/vuln/detail/CVE-2026-33634
- rosesecurity.dev/2026/03/20/typosquatting-trivy.html
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-33634
- www.microsoft.com/en-us/security/blog/2026/03/24/detecting-investigating-defending-against-trivy-supply-chain-compromise
- www.wiz.io/blog/teampcp-attack-kics-github-action
Code Behaviors & Features
Detect and mitigate CVE-2026-33634 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →