VULNpocalypse

CVE-2026-33634: Aquasecurity Trivy Embedded Malicious Code Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

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 to 0.34.2 (76/77), and the`aquasecurity/setup-trivy` GitHub Action versions 0.2.0 to 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 to 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.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-03-23).

Weakness: CWE-506: Embedded Malicious Code

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.

On CISA KEV since
2026-03-26
US federal deadline
2026-04-09
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2026-03951, EUVD-2026-14601, GHSA-69fq-xp46-6x23

VEDAS cluster: VEDAS:GAUNTLETGLADE

Exploit Observer links 2 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (2)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Vulnerability databases and vendor advisories (7)

Catalogue entries, not exploit evidence.

18 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.597
very likely to be attacked soon
VEDAS
0.973
strong exploit evidence
On CISA KEV
Yes, since 2026-03-26
Detection rule
None yet
EPSS (chance of attack)
100.1CVE-2026-33634 EPSS over time2026-082026-11-01
VEDAS (exploit evidence)
100.9CVE-2026-33634 VEDAS over time2026-082026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
aquasecurity setup-trivyversion < 0.2.6Not stated
aquasecurity trivy-actionversion < 0.35.0Not stated
aquasecurity trivyversion = 0.69.4Not stated
BerriAI LiteLLMversion >= 1.82.7, <= 1.82.8Not stated
team-telnyx telnyxversion >= 4.87.1, <= 4.87.2Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: aqua_security_software_ltd. setup-trivy, aqua_security_software_ltd. trivy, aqua_security_software_ltd. trivy-action, aquasec setup-trivy, aquasec trivy, aquasec trivy_action, github_actions aquasecurity/setup-trivy, github_actions aquasecurity/trivy-action, go github.com/aquasecurity/trivy, litellm litellm.

How to fix it

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.

Vendor guidance:

How to detect it

There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.

Advisories on this CVE

References

Exploits and technical analysis

Government sources

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.