Skip to content
Server Security Center
KEVcritical9.4

CVE-2026-33634: Aquasecurity Trivy Embedded Malicious Code

Aquasecurity Trivy · listed in the CISA catalog of actively exploited vulnerabilities since 2026-03-26.

CVSS v4.0 (CVE record)
9.4
critical
EPSS (exploit probability, 30 days)
62%
higher than 99.1% of all CVEs
Added to CISA KEV
2026-03-26
US federal due date 2026-04-09
Automatable (CISA SSVC)
no
technical impact: total

CVE-2026-33634 explained

CVE-2026-33634 is an embedded malicious code issue in Aquasecurity Trivy, a security scanner. Using compromised credentials, a threat actor published a malicious Trivy 0.69.4 release and pointed version tags of the trivy-action and setup-trivy GitHub Actions to credential-stealing malware. Any pipeline that ran these components may have exposed its secrets.

Impact

A compromised Trivy binary or GitHub Action running in a pipeline can steal secrets that the pipeline can access. CISA rates the technical impact as total. It is not automatable, which means exploitation does not scale without manual steps. CISA lists the vulnerability as known exploited. The description states that a fallback exfiltration mechanism may have stolen secrets successfully, so affected organizations should treat all reachable credentials as exposed.

Who is affected

The CVE record lists aquasecurity trivy 0.69.4, aquasecurity trivy-action < 0.35.0 and aquasecurity setup-trivy < 0.2.6. It also lists BerriAI LiteLLM (≥ 1.82.7, ≤ 1.82.8) and team-telnyx telnyx (≥ 4.87.1, ≤ 4.87.2). The record names no fixed version. The description names these known safe versions: Trivy 0.69.2 and 0.69.3, trivy-action 0.35.0, and setup-trivy 0.2.6 as recreated with a safe commit.

Written with AI from the data on this page and checked against it automatically.

Official 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 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.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • aquasecurity setup-trivy
    Affected
    • < 0.2.6
    Fixed in
    not stated
  • aquasecurity trivy-action
    Affected
    • < 0.35.0
    Fixed in
    not stated
  • aquasecurity trivy
    Affected
    • 0.69.4
    Fixed in
    not stated
  • BerriAI LiteLLM
    Affected
    • ≥ 1.82.7
    • ≤ 1.82.8
    Fixed in
    not stated
  • team-telnyx telnyx
    Affected
    • ≥ 4.87.1
    • ≤ 4.87.2
    Fixed in
    not stated

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: github.com/aquasecurity/trivy/security/advisories/GHSA-69…
  • CISA's deadline for US federal agencies: 2026-04-09 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Check whether your organization pulled or executed Trivy 0.69.4 from any source, and remove affected artifacts immediately.
  2. Move to a known safe version: Trivy 0.69.2 or 0.69.3, trivy-action 0.35.0, or setup-trivy 0.2.6.
  3. If a compromised version may have run, treat all secrets accessible to affected pipelines as exposed and rotate them immediately.
  4. Review workflows using trivy-action or setup-trivy. Where they referenced version tags, check run logs from March 19–20, 2026 for signs of compromise.
  5. Look for repositories named tpcp-docs in your GitHub organization. Their presence may indicate that secrets were stolen.
  6. Pin GitHub Actions to full, immutable commit SHA hashes instead of mutable version tags.

The CVE record names no fixed version. Use the known safe versions named in the description and follow the vendor advisory. CISA requires applying mitigations per vendor instructions and following BOD 22-01 guidance for cloud services. If mitigations are unavailable, CISA requires discontinuing use of the product. Rotate any secrets that may have been exposed.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-506 Embedded Malicious Code

Questions about CVE-2026-33634

Is this vulnerability being exploited?
Yes. CISA added CVE-2026-33634 to its Known Exploited Vulnerabilities catalog on 2026-03-26. The US federal due date is 2026-04-09. Whether it has been used in ransomware is unknown.
We referenced trivy-action by version tag. Are we affected?
Possibly. The attacker force-pushed 76 of 77 trivy-action tags and all 7 setup-trivy tags to malicious commits. Check workflow run logs from March 19–20, 2026, rotate exposed secrets, and pin to full commit SHAs.
Why was the attacker able to strike again after the first disclosure?
According to the description, credential rotation after the March 1 disclosure was not atomic. During a rotation window of a few days, the attacker could have used a valid token to exfiltrate newly rotated secrets and keep access.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.