TrivyApplication · Aquasec
CVE-2026-33634
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTrivy 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a supply chain attack on the Trivy security scanner where attackers used compromised credentials to publish a malicious v0.69.4 release and replace 76 of 77 version tags in trivy-action and all 7 tags in setup-trivy with credential-stealing malware. The attack was possible because credential rotation was not atomic, allowing the attacker to exfiltrate newly rotated secrets during a multi-day rotation window.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
TrivyApplication
= 0.69.4
TelnyxApplication
= 4.87.1= 4.87.2< 0.2.6< 0.35.0= 1.82.7= 1.82.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Trivy versionRun 'trivy --version' or inspect the binary/path used in your CI/CD pipeline to identify the exact version numberAffected if The installed or executed version is exactly 0.69.4 (the malicious release)
-
Inspect GitHub Actions workflow files for Trivy ActionReview all .yml/.yaml files in .github/workflows/ directories for 'uses: aquasec/trivy-action@' and note the tag or commit SHAAffected if The Trivy Action version is < 0.35.0 (all versions were compromised in the attack)
-
Inspect GitHub Actions workflow files for Setup TrivyReview workflow files for 'uses: aquasec/setup-trivy@' and check the version tag specifiedAffected if Setup Trivy version is < 0.2.6
-
Check for Telnyx library usageReview your application dependencies, package-lock.json, or requirements.txt for 'telnyx' package and its versionAffected if Telnyx version is exactly 4.87.1 or 4.87.2
-
Check for Litellm library usageReview dependencies for 'litellm' package and its version numberAffected if Litellm version is exactly 1.82.7 or 1.82.8
-
Examine CI/CD execution logs for compromise indicatorSearch GitHub Actions logs, build artifacts, or pipeline run history for references to 'tpcp-docs' repository as an indicator of the credential-stealing malware executionAffected if Logs or artifacts contain references to 'tpcp-docs' repository indicating the malicious payload was executed
You are affected if any of these conditions are true: Trivy v0.69.4 was executed, Trivy Action < 0.35.0 or Setup Trivy < 0.2.6 was used in workflows, Telnyx 4.87.1/4.87.2 or Litellm 1.82.7/1.82.8 were used, or CI/CD logs show evidence of the tpcp-docs compromise indicator.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.2.60.35.0
Organizations must immediately check if Trivy v0.69.4 was pulled or executed, review workflow logs from March 19-20, 2026 for compromise indicators, look for a 'tpcp-docs' repository (sign of successful exfiltration), rotate all secrets accessible to affected pipelines, and pin GitHub Actions to immutable commit SHA hashes instead of mutable version tags.
Trivy: upgrade to 0.69.2 or 0.69.3; aquasecurity/trivy-action: upgrade to 0.35.0; aquasecurity/setup-trivy: upgrade to 0.2.6
- 1. Immediately stop using and remove Trivy v0.69.4 from all environments
- 2. Upgrade Trivy to version 0.69.2 or 0.69.3 (known safe versions)
- 3. Upgrade aquasecurity/trivy-action to version 0.35.0 (the first safe version)
- 4. Upgrade aquasecurity/setup-trivy to version 0.2.6 (recreated with safe commit)
- 5. Rotate all secrets, tokens, and credentials that were accessible to affected CI/CD pipelines since February 2026
- 6. Check organization logs for any access from March 19-20, 2026 and review for signs of compromise
- 7. Search GitHub organization for any repository named 'tpcp-docs' - if found, secrets should be considered compromised
- 8. Review all workflow files that reference aquasecurity/trivy-action or aquaseecurity/setup-trivy
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Trivy
Exploited in the wild — priority engagement
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33634 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33634 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data