CVE Intelligence
Skip to main content
CISA KEVhighpublic exploit

CVE-2026-33634

CVE-2026-33634 — Trivy ecosystem supply chain briefly compromised

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.

Published Updated Sources: NVD, aquasecurity (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Mar 26, 2026

EPSS

59%

ahead of 99.1% of scored CVEs

Affects

aquasecurity

5 products listed

CVSS base

8.8

high · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade setup-trivy to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

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.

Federal deadline Apr 9, 2026 — passed 162 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Treat as emergency remediation because CISA KEV status is present.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
aquasecuritysetup-trivy< 0.2.6Vulnerable
aquasecuritytrivy-action< 0.35.0Vulnerable
aquasecuritytrivy= 0.69.4Vulnerable
BerriAILiteLLM>= 1.82.7, <= 1.82.8Vulnerable
team-telnyxtelnyx>= 4.87.1, <= 4.87.2Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
8.8CVSS 3.1high2.85.9NVD
9.4CVSS 4.0critical——aquasecurity (CNA)

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-506 · Embedded Malicious Code

  • Execute Unauthorized Code or Commands::

Mitigation: Remove the malicious code and start an effort to ensure that no more malicious code exists. This may require a detailed review of all code, as it is possible to hide a serious attack in only one or two lines of code. These lines may be located almost anywhere in an application and may have been intentionally obfuscated by the attacker.::

Weakness & attack patterns

  • CWE-506

Inferred from the weakness class — not observed against this CVE.

  • T1195.001Supply Chain Compromise: Compromise Software Dependencies and Development Tools
  • T1195.002Supply Chain Compromise: Compromise Software Supply Chain
  • T1027.009Obfuscated Files or Information: Embedded Payloads

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Mar 26, 2026

Federal deadline

Apr 9, 2026

passed 162 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

49

1 of the 5 sampled are weaponized

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

SOCRadar35 more posts on this CVEShowing 5 of 40 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /trivy-action, /setup-trivy, /trivy, /77).
  • Prioritize edge telemetry for network-reachable setup-trivy, trivy-action, trivy, LiteLLM, telnyx.
  • Monitor for scanner or exploit-pattern traffic after 49 public PoC repositories were reported.
web/proxy/WAF logsapplication logsnetwork IDS/IPS

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

TeamPcp
  • hostnamecheckmarx.zone92

    Maltrail Malware Feeds · Mar 24, 2026

  • hostnamemodels.litellm.cloud89

    Maltrail Malware Feeds · Mar 24, 2026

  • urlhttps://checkmarx.zone/raw71

    AlienVault OTX Feeds · Mar 24, 2026

  • ip37.27.244.22278

    usom.phishing-General-List · Mar 19, 2026

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026

  2. Added · CVSS 3.1 8.8 (AV:N)

    Jun 17, 2026 · NVD

  3. Added to CISA KEV catalog

    Mar 26, 2026 · CISA

  4. Initial · CVE published

    Mar 23, 2026 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

  • 25×SVRS was changedApr 4, 2026 – Jul 22, 2026 · SOCRadar CTI
  • 11×TweetsApr 7, 2026 – Jul 3, 2026 · SOCRadar CTI
  • 1×Github_Repos · Github repository created, dfs333/trivysupplychainanalysisJul 15, 2026 · SOCRadar CTI

References

19 on the record

Coverage

20 stories from the feeds we poll

SOCRadar15 more reports on this CVEShowing 5 of 20 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • Only the 4 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-33634 is Trivy ecosystem supply chain briefly compromised, a high vulnerability affecting setup-trivy, trivy-action, trivy, LiteLLM, telnyx from aquasecurity, BerriAI, team-telnyx. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 49 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.8 describes technical severity, while EPSS 59% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.