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.

This CVE was assigned for the supply chain attack targeting the Trivy security scanner and downstream projects. Please refer to the advisory for mitigation guidance.

The version of the LiteLLM Python package installed on the remote host is 1.82.7 or 1.82.8. These versions were published to PyPI by a threat actor known as TeamPCP using compromised maintainer credentials obtained through the Aqua Security Trivy supply chain attack. The malicious releases contain credential-stealing malware designed to exfiltrate secrets such as SSH keys, cloud credentials, environment variables, and Kubernetes secrets from the environment where LiteLLM is installed. It is, therefore, affected by a vulnerability:

  - A threat actor used compromised PyPI credentials to publish malicious LiteLLM versions 1.82.7 and 1.82.8     containing an infostealer payload. Version 1.82.7 injected the payload into the proxy server module, while     version 1.82.8 used a .pth file to execute malicious code on any Python interpreter startup. Collected data was     encrypted and exfiltrated to an attacker-controlled domain. If a compromised version was installed, all secrets     accessible to the affected environment must be treated as exposed and rotated immediately. (CVE-2026-33634)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of Aqua Security Trivy installed on the remote host is 0.69.4. This version was published by a threat actor using compromised credentials as part of a supply chain attack. The malicious release contains credential-stealing malware designed to exfiltrate secrets such as SSH keys, cloud credentials, and cryptocurrency wallets from the environment where Trivy is executed. It is, therefore, affected by a vulnerability:

  - A threat actor used compromised credentials to publish a malicious Trivy v0.69.4 release containing an infostealer.
    If a compromised version ran in an environment, all secrets accessible to affected pipelines must be treated as     exposed and rotated immediately. (CVE-2026-33634)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
304806	LiteLLM 1.82.7 / 1.82.8 Supply Chain Compromise (GHSA-5mg7-485q-xm76)	Nessus	Artificial Intelligence	critical
303932	Aqua Security Trivy 0.69.4 Supply Chain Compromise (GHSA-69fq-xp46-6x23)	Nessus	Misc.	critical

Detections

Analytics

CVE-2026-33634

critical

Tenable Plugins

critical

critical