Skip to content
Fencer Vulns
high 8.8

CVE-2026-33634 kev in the critical feed json

Trivy ecosystem supply chain briefly compromised

published 2026-03-23 7 mo ago modified 2026-11-05 3 d ago also EUVD-2026-14601 , GHSA-69fq-xp46-6x23 , GO-2026-4919

cvss
8.8
version 3.1, NVD
cisa kev
Exploited
added 2026-03-26
epss
59.7%
EPSS 59.7% chance of exploitation in 30 days, percentile 99.1%
public exploits
0
none known

Summary

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.

Patch / fix

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.

  • go github.com/aquasecurity/trivy 0.70.0
  • github-actions aquasecurity/trivy-action 0.35.0
  • github-actions aquasecurity/setup-trivy 0.2.6
  • aquasec setup-trivy 0.2.6
  • aquasec trivy_action 0.35.0
  • litellm litellm 1.83.0
  • telnyx telnyx 4.88.0
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20260402T184258-150000.1.158.1

suse advisories SUSE-SU-2026:1205-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Timeline

  1. Published
  2. CISA SSVC: exploitation active
  3. Added to CISA KEV
  4. CISA patch deadline

Known exploited

Added
7 mo ago
Patch by
2026-04-09 (7 mo ago)
Ransomware
Not known
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, product
Aquasecurity, Trivy
CISA name
Aquasecurity Trivy Embedded Malicious Code Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
7 mo ago

Exploit prediction

59.73% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • rosesecurity.dev https://rosesecurity.dev/2026/03/20/typosquatting-trivy.html referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 9.4 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
CNA 4.0 9.4 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
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/aquasecurity/trivy
1 listed version
>=0.69.4, <0.70.0
0.70.0
github-actions aquasecurity/trivy-action
<0.35.0
0.35.0
github-actions aquasecurity/setup-trivy
<0.2.6
0.2.6

Affected products

  • aquasecurity setup-trivy
  • aquasecurity trivy-action
  • aquasecurity trivy
  • BerriAI LiteLLM
  • team-telnyx telnyx

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.