Skip to main content

Aqua Security Trivy GitHub Action Compromised

Aqua Security's Trivy binaries and GitHub actions have been compromised and could harvest secrets

Threat ID:
CC-4758
Threat Severity:
Medium
Published:
20 March 2026 4:18 PM
Report a cyber attack: call 0300 303 5222 or email [email protected]

Summary

Aqua Security's Trivy binaries and GitHub actions have been compromised and could harvest secrets

Affected platforms

The following platforms are known to be affected:

  • Trivy binary and Container Images
  • trivy-action GitHub action
  • setup-trivy GitHub action

Please see GHSA-69fq-xp46-6x23 for affected versions.

Threat details

Introduction

Security researchers have identified a supply-chain compromise affecting Aqua Security's Trivy, a widely used vulnerability scanning tool. Compromised versions point to malicious code which could be used as an information stealer to extract secrets and credentials from an affected system.

  • CVE-2026-33634 - Embedded Malicious Code vulnerability - CVSSv4 base score: 9.4

Review GHSA-69fq-xp46-6x23 for latest information

The response effort for the compromise of the Trivy project is ongoing and available information may change rapidly. Please review GHSA-69fq-xp46-6x23 for the latest information.

Threat updates

Date Update
24 Mar 2026 CVE-2026-33634 assigned

The following sections have been updated to reflect new information:

  • Introduction
  • CVE Vulnerabilities
23 Mar 2026 Trivy has released an official advisory for the compromise.

The following sections have been updated to reflect new information:

  • Affected platforms
  • Introduction
  • Remediation
  • Remediation Steps
  • Added information box

Remediation advice

The NHS England National CSOC recommends impacted organisations review the Trivy advisory GHSA-69fq-xp46-6x23 follow the remediation steps detailed below.

Remediation steps

Type Step
Patch

Update to known safe versions:

Trivy binary

  • Version: v0.69.2 and v0.69.3

trivy-action

  • Version: v0.35.0

setup-trivy

  • Version: v0.2.6

 

Note: New tags have been published with a v prefix (v0.0.1 – v0.34.2) pointing to the original legitimate commits. Old versions without a v prefix should be considered compromised (0.0.1 – 0.34.2).


https://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23
Guidance

Reset Secrets:

Any pipeline that executed an affected action, binary, or container image should be considered fully compromised and all secrets should be reset. Exposure windows are provided in GHSA-69fq-xp46-6x23.

For self-hosted GitHub runners, any additional credentials stored on the device's filesystem should be reset.


https://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23

CVE Vulnerabilities

Status Published

CVE-2026-33634

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.

Last edited: 24 March 2026 9:43 am