CVE-2026-33634

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering, service disruption.

In the wild

CISA lists this as exploited in real attacks. Treat as urgent.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-03-23 14:24 UTC ReservedThe CVE id was reserved by its CNA
2. 2026-03-23 22:16 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-03-26 Exploited in the wildAdded to CISA's Known Exploited Vulnerabilities list
4. 2026-04-09 Remediation deadlineCISA's due date for federal agencies to fix it
5. 2026-06-17 10:37 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: yes, CISA lists it. This puts it above everything that is not.
• Exploit odds: 60.4% in the next 30 days (EPSS).
• Severity: 9.4 CRITICAL (CVSS).
• Fix: a patch or advisory is linked.
• It meets the bar for Drop everything: critical, and exploited or very likely to be.

Details

Published

2026-03-23 22:16 UTC

Last modified

2026-06-17 10:37 UTC

Added to CISA KEV

2026-03-26

Exploit probability

60.4% · EPSS, next 30 days

Weakness

CWE-506

Record status

Analyzed

Affected

• Aquasec setup-trivy < 0.2.6
• Aquasec Trivy 0.69.4
• Aquasec Trivy Action < 0.35.0
• Litellm 1.82.7
• Litellm 1.82.8
• Telnyx 4.87.1
• Telnyx 4.87.2

Attack profile CVSS 4.0 · 9.4

Attack vector

Network

Complexity

Low

Attack requirements

None

Privileges needed

Low

User interaction

None

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-33634.md and follow it. Check whether this project is affected by CVE-2026-33634. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge