Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-33634: Trivy Ecosystem Supply-Chain Compromise

Published Mar 23, 2026 · Updated 23 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS9.4Critical · v4
EPSS61.5%99th percentile
CISA KEVYesAdded Mar 26, 2026
In the wildActivePer CISA KEV
Vendors
LitellmAquasecTelnyx
IdentifiersCVE-2026-33634CWE-506 · Embedded Malicious Code
Also known asghsa_69fq_xp46_6x23

CVE-2026-33634 identifies a software supply-chain compromise affecting Aqua Security Trivy and its associated GitHub Actions. On March 19, 2026, attackers used compromised credentials to publish malicious Trivy 0.69.4 artifacts, redirect 76 of 77 trivy-action version tags to credential-stealing code, and replace all seven setup-trivy version tags with malicious commits. The affected Action ranges were trivy-action 0.0.1–0.34.2, with one tag unaffected, and setup-trivy 0.2.0–0.2.6 before the safe recreation of 0.2.6. Malicious Trivy container images tagged 0.69.5 and 0.69.6 were subsequently distributed through Docker Hub. Non-atomic credential rotation following an earlier compromise may have allowed attackers to capture replacement credentials and retain access. The malicious components executed credential-harvesting code in environments running otherwise trusted security tooling. Downstream compromise of LiteLLM publishing credentials resulted in malicious releases 1.82.7 and 1.82.8, which were subsequently included among the affected software associated with the CVE. The incident is attributed to TeamPCP, also tracked as UNC6780.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Execution of compromised artifacts exposed secrets accessible to affected CI/CD runners and hosts, including source-control and package-publishing tokens, cloud credentials, SSH private keys, Kubernetes credentials, database passwords, and AI-provider API keys. The Trivy payload harvested filesystem and environment secrets and read runner process memory, bypassing the protection afforded by log secret masking. Stolen credentials enabled unauthorized cloud and repository access, data exfiltration, and further software supply-chain compromises. The downstream LiteLLM 1.82.8 package additionally enabled malicious execution during Python interpreter startup without an explicit LiteLLM import. Exposure is bounded by the permissions and resources available to the compromised execution environment; installing a clean release does not invalidate credentials already stolen.

Mitigation

If you can’t patch tonight, do this now.

Pin GitHub Actions to verified, full immutable commit SHAs rather than mutable version tags, and pin container images to verified clean digests. Review affected workflow execution logs, particularly March 19–20, 2026, and investigate use of the subsequently poisoned Docker Hub images on March 22–23. Search GitHub organizations for unexpected repositories named tpcp-docs or docs-tpcp, including timestamp-prefixed variants, which were used for fallback exfiltration. Block known campaign exfiltration infrastructure and monitor for unusual runner-memory access, bulk credential collection, encrypted archive creation, and unexpected outbound transfers during builds. Restrict pipeline credentials and permissions to reduce the consequences of executing compromised dependencies.

Remediation

Patch, then assume compromise.

Remove compromised Trivy binaries, container images, GitHub Action references, and cached artifacts. Replace them with verified clean artifacts: Trivy 0.69.2 or 0.69.3, trivy-action 0.35.0, and setup-trivy 0.2.6 after its recreation with the safe commit. Do not infer safety from a numerically higher container tag, because Docker Hub tags 0.69.5 and 0.69.6 were also compromised. Replace malicious LiteLLM 1.82.7 and 1.82.8 installations with a verified clean release, such as 1.82.6, and rebuild affected environments to eliminate malicious startup hooks and persistence. Immediately revoke and rotate every secret accessible to an affected pipeline or host. Coordinate revocation and replacement so surviving attacker access cannot retrieve newly issued credentials. Investigate unauthorized account activity, repository changes, cloud access, and downstream artifacts produced using potentially exposed publishing credentials.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit.

View more in app →
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AquasecSetup-Trivyapplication
AquasecTrivyapplication
AquasecTrivy Actionapplication
LitellmLitellmapplication
TelnyxTelnyxapplication
FAQ

Frequently asked questions

Is CVE-2026-33634 exploited in the wild?
Yes. As of Oct 25, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 26, 2026.
Is there a public exploit for CVE-2026-33634?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-33634, the earliest disclosed Sep 21, 2026.
Is there a patch for CVE-2026-33634?
Remove compromised Trivy binaries, container images, GitHub Action references, and cached artifacts. Replace them with verified clean artifacts: Trivy 0.69.2 or 0.69.3, trivy-action 0.35.0, and setup-trivy 0.2.6 after its recreation with the safe commit.
What products are affected by CVE-2026-33634?
Litellm, Aquasec Setup-Trivy, Aquasec Trivy, Telnyx, and Aquasec Trivy Action.
How severe is CVE-2026-33634?
CVE-2026-33634 has a CVSS v4 score of 9.4 (Critical) and an EPSS score of 61.5% (99th percentile) as of Oct 25, 2026.
Activity feed

Recent activity

111 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+58 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence75Every report linking this CVE to a named adversary.
Associated malware69Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity46Community discussion across Reddit, Mastodon, and other social sources.