Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.4Exploited · CISA KEV

Trivy ecosystem supply chain was briefly compromised

CVE-2026-33634GHSA-69fq-xp46-6x23

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • GitHub Actions aquasecurity/setup-trivy

    Affected
    < 0.2.6
    Fixed in
    0.2.6

  • Go github.com/aquasecurity/trivy

    Affected
    >= 0.69.4, <= 0.69.4
    Fixed in
    no fixed version recorded

  • GitHub Actions aquasecurity/trivy-action

    Affected
    < 0.35.0
    Fixed in
    0.35.0

Sources

Severity and exploitation
Exploitation
Confirmed: listed in the CISA Known Exploited Vulnerabilities catalog.
CVSS 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 · score source
EPSS
  • CVE-2026-33634: 59.73% estimated exploitation activity in the next 30 days; percentile 99.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. On March 22, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.5 and v0.69.6 DockerHub images. Exposure Window | Component | Start (UTC) | End (UTC) | Duration | | ------------- | ---------------------- | ----------------- | --------- | | trivy v0.69.4 | 2026-03-19 18:22 [^1] | 2026-03-19 ~21:42 | ~3 hours | | trivy-action | 2026-03-19 ~17:43 [^2] | 2026-03-20 ~05:40 | ~12 hours | | setup-trivy | 2026-03-19 ~17:43 [^2] | 2026-03-19 ~21:44 | ~4 hours | | dockerhub trivy images v0.69.5 and v0.69.6 | 2026-03-22 15:43 | 2026-03-23 ~01:40 | ~10 hours | [^1]: Time when v0.69.4 release artifacts became publicly available. The malicious tag was pushed at ~17:43 UTC, triggering…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-69fq-xp46-6x23

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33634

Advisory: Trivy ecosystem supply chain was briefly compromised
IDs: CVE-2026-33634, GHSA-69fq-xp46-6x23
Record: https://patchnext.com/advisories/cve-2026-33634 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.4)
Exploitation: confirmed: listed in the CISA Known Exploited Vulnerabilities catalog.
Vendor response: Partial vendor fix; fixed versions by package: aquasecurity/setup-trivy 0.2.6; aquasecurity/trivy-action 0.35.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- GitHub Actions aquasecurity/setup-trivy: affected < 0.2.6; fixed in 0.2.6
- Go github.com/aquasecurity/trivy: affected >= 0.69.4, <= 0.69.4
- GitHub Actions aquasecurity/trivy-action: affected < 0.35.0; fixed in 0.35.0

## Suggested inspection (read-only)
- GitHub Actions aquasecurity/setup-trivy: check the installed version with your package manager.
- Go github.com/aquasecurity/trivy: check the installed version with your package manager.
- GitHub Actions aquasecurity/trivy-action: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on aquasecurity/setup-trivy, github.com/aquasecurity/trivy, aquasecurity/trivy-action.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-69fq-xp46-6x23 (GitHub-reviewed advisory GHSA-69fq-xp46-6x23 lists affected ranges: Go github.com/aquasecurity/trivy >=0.69.4 =0 =0 <0.2.6)
- Verified: https://www.cisa.gov/known-exploited-vulnerabilities-catalog (CISA added CVE-2026-33634 to the Known Exploited Vulnerabilities catalog on 2026-03-26.)

Commands are suggestions: review each one before running it.

Loading voting…