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

Exp

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: 2026-03-23 Last update: 2026-03-30 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-33634 is rated Critical Active Threat (91.2/100): CVSS Critical severity, with high exploitation likelihood (EPSS 23.90%, 96th percentile). Core evidence: CISA KEV confirms active exploitation (added 2026-03-26) affecting Aquasecurity / Trivy. a weakness (CWE-506) Unauthenticated remote administrative access may be possible. Mandatory action: The CISA remediation deadline has passed—treat as an emergency patch priority.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

CISA KEV Record for CVE-2026-33634

Name: Aquasecurity Trivy Embedded Malicious Code Vulnerability · CISA KEV detail

Exploit added: 2026-03-26

Action due: 2026-04-09

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.

Public exploit references (Exploit-DB) for CVE-2026-33634

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2026-33634

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-03 29.36% 23.90% -5.46%
2 2026-05-30 26.59% 29.36% +2.77%
3 2026-05-23 26.59%

Full EPSS history (16 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-33634

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.4 4.0 CRITICAL
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network.
Attack complexity (AC:L)
Exploitation conditions are straightforward and stable.
Attack requirements (AT:N)
No additional preconditions are required beyond normal reachability.
Privileges required (PR:L)
Low privileges are required.
User interaction (UI:N)
No user interaction is required.
Vulnerable system confidentiality impact (VC:H)
High confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:H)
High integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:H)
High availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:H)
High confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:H)
High integrity impact on subsequent systems.
Subsequent system availability impact (SA:H)
High availability impact on subsequent systems.
Exploit maturity (threat) (E:X)
Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X)
Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X)
Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X)
Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X)
Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X)
Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X)
Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X)
Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X)
Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X)
Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X)
Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X)
Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X)
Not evaluated.
Automatable (supplemental) (AU:X)
Not evaluated.
Recovery (supplemental) (R:X)
Not evaluated.
Value density (supplemental) (V:X)
Not evaluated.
Vulnerability response effort (supplemental) (RE:X)
Not evaluated.
Provider urgency (supplemental) (U:X)
Not evaluated.
[email protected]
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8 5.9 [email protected]

Weakness enumeration for CVE-2026-33634

GitHub Security Advisory for CVE-2026-33634

GHSA-69fq-xp46-6x23 · Severity: critical · Ecosystem: go — Trivy ecosystem supply chain was briefly compromised

OS Trackers for CVE-2026-33634

vendor priority summary link
suse critical https://www.suse.com/security/cve/CVE-2026-33634/

Affected software / configurations for CVE-2026-33634

Vendor Product Version Raw CPE
aquasec setup-trivy < 0.2.6 cpe:2.3:a:aquasec:setup-trivy:*:*:*:*:*:*:*:*
aquasec trivy 0.69.4 cpe:2.3:a:aquasec:trivy:0.69.4:*:*:*:*:go:*:*
aquasec trivy_action < 0.35.0 cpe:2.3:a:aquasec:trivy_action:*:*:*:*:*:*:*:*
litellm litellm 1.82.7 cpe:2.3:a:litellm:litellm:1.82.7:*:*:*:*:*:*:*
litellm litellm 1.82.8 cpe:2.3:a:litellm:litellm:1.82.8:*:*:*:*:*:*:*
telnyx telnyx 4.87.1 cpe:2.3:a:telnyx:telnyx:4.87.1:*:*:*:*:python:*:*
telnyx telnyx 4.87.2 cpe:2.3:a:telnyx:telnyx:4.87.2:*:*:*:*:python:*:*

References for CVE-2026-33634

URL Tags
https://docs.litellm.ai/blog/security-update-march-2026 Third Party Advisory
https://futuresearch.ai/blog/litellm-pypi-supply-chain-attack Third Party Advisory
https://github.com/BerriAI/litellm/issues/24518 Issue Tracking Mitigation Third Party Advisory
https://github.com/aquasecurity/trivy/discussions/10425 Issue Tracking Vendor Advisory
https://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23 Exploit Mitigation Vendor Advisory
https://github.com/pypa/advisory-database/tree/main/vulns/litellm/PYSEC-2026-2.yaml Third Party Advisory
https://github.com/team-telnyx/telnyx-python/security/advisories/GHSA-955r-262c-33jc Third Party Advisory
https://inspector.pypi.io/project/litellm/1.82.7/packages/79/5f/b6998d42c6ccd32d36e12661f2734602e72a576d52a51f4245aef0b20b4d/litellm-1.82.7-py3-none-any.whl/litellm/proxy/proxy_server.py#line.130 Broken Link
https://inspector.pypi.io/project/litellm/1.82.8/packages/f6/2c/731b614e6cee0bca1e010a36fd381fba69ee836fe3cb6753ba23ef2b9601/litellm-1.82.8.tar.gz/litellm-1.82.8/litellm_init.pth#line.1 Broken Link
https://www.wiz.io/blog/teampcp-attack-kics-github-action Not Applicable
https://github.com/BerriAI/litellm/issues/24518#issuecomment-4127436387 Issue Tracking Mitigation Third Party Advisory
https://rosesecurity.dev/2026/03/20/typosquatting-trivy.html Exploit Third Party Advisory
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-33634 US Government Resource
https://www.microsoft.com/en-us/security/blog/2026/03/24/detecting-investigating-defending-against-trivy-supply-chain-compromise/ Technical Description
cvelogic Threat Intelligence