← Übersicht GitHub Actions

Trivy ecosystem supply chain briefly compromised

CVE-2026-33634 · GHSA-69fq-xp46-6x23 · GO-2026-4919 · WID-SEC-W-2026-0898

Aktiv ausgenutzt (CISA KEV) Kritisch · CVSS 9.4 BSI: kritisch Netzwerk · mit Login Fix verfügbar

Aktive Ausnutzung bestätigt.

CISA führt diese Schwachstelle seit 26.03.2026 im Katalog der ausgenutzten Schwachstellen. Frist für US-Bundesbehörden: 09.04.2026.

Vorgabe von CISA: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Veröffentlicht
23.03.2026 22:47
Zuletzt geändert
06.11.2026
EPSS (30 Tage)
62.0 %
CVSS-Vektor
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

Beschreibung

Originaltext der Quelle, nicht übersetzt.

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.

Status beim Hersteller

BSI stuft seine Produktlinien ein: 5 betroffen.

Aqua Security Trivy 0.69.4 Betroffen
Aqua Security Trivy Container Image 0.69.5 Betroffen
Aqua Security Trivy Container Image 0.69.6 Betroffen
Aqua Security Trivy setup-trivy <0.2.6 Betroffen
Aqua Security Trivy trivy-action <0.35.0 Betroffen

Betroffene Pakete im beobachteten Stack

GitHub Actionsaquasecurity/setup-trivy0.2.6GHSA-69fq-xp46-6x23
GitHub Actionsaquasecurity/trivy-action0.35.0GHSA-69fq-xp46-6x23
Weitere betroffene Pakete (17)
CVEBerriAI/LiteLLMkein Fix bekanntCVE-2026-33634
CVEaquasecurity/setup-trivykein Fix bekanntCVE-2026-33634
CVEaquasecurity/trivykein Fix bekanntCVE-2026-33634
CVEaquasecurity/trivy-actionkein Fix bekanntCVE-2026-33634
CVEteam-telnyx/telnyxkein Fix bekanntCVE-2026-33634
Gogithub.com/aquasecurity/trivykein Fix bekanntGHSA-69fq-xp46-6x23
Gogithub.com/aquasecurity/trivy0.69.4 → 0.70.0GO-2026-4919
NVDaquasec:setup-trivy0.2.6CVE-2026-33634
NVDaquasec:trivykein Fix bekanntCVE-2026-33634
NVDaquasec:trivy_action0.35.0CVE-2026-33634
NVDlitellm:litellmkein Fix bekanntCVE-2026-33634
NVDtelnyx:telnyxkein Fix bekanntCVE-2026-33634
SUSE:Linux Enterprise Server 16.0govulncheck-vulndb0.0.20261105T234957-160000.1.1SUSE-SU-2026:24730-1
SUSE:Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20261105T234957-160000.1.1SUSE-SU-2026:24730-1
openSUSE:Leap 15.6govulncheck-vulndb0.0.20260402T184258-150000.1.158.1SUSE-SU-2026:1205-1
openSUSE:Leap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
openSUSE:Leap 16.0govulncheck-vulndb0.0.20261105T234957-160000.1.1openSUSE-SU-2026:22336-1

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · mit Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.