Threat Intelligence / CVE / CVE-2026-33634

CVE-2026-33634 — Aquasec Setup-trivy

CISA KEV

CVSS v3.1 8.8 (HIGH) · CVSS v4.0 9.4 · EPSS 21.1% (higher than 95.6% of all scored CVEs) · Priority 9/10 · Published 2026-03-23

As of 2026-03-30, CVE-2026-33634 is a HIGH-severity vulnerability in Aquasec Setup-trivy, CVSS v3.1 8.8, EPSS 21.1% (95.6th percentile). It is listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-03-26), with a US federal remediation deadline of 2026-04-09. Threadlinqs Intelligence links 4 tracked threat campaigns to CVE-2026-33634, most recently “TeamPCP LiteLLM Supply Chain Attack — Trojaned PyPI Packages (v1.82.7/1.82.8) with Multi-Stage C2 Payload”.

Last updated: 2026-03-30

What is CVE-2026-33634?

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.

The record classifies CVE-2026-33634 under weakness class CWE-506. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity, availability. 7 affected-product entries are recorded, across 3 vendors, listed below. The identifier was first published 173 days ago.

Severity and exploitation probability

CVSS v3.1 base score: 8.8 — HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0 base score: 9.4
EPSS (FIRST): 21.1% probability of exploitation in the next 30 days, higher than 95.6% of all scored CVEs
CISA KEV: Listed since 2026-03-26, federal remediation deadline 2026-04-09
Threadlinqs priority: 9/10 — CISA KEV-listed, which Threadlinqs floors at 9
Published: 2026-03-23, last modified 2026-03-30

Is CVE-2026-33634 being exploited?

CISA added CVE-2026-33634 to the Known Exploited Vulnerabilities catalog on 2026-03-26, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2026-04-09 under BOD 22-01. It currently carries a trending score of 49 in the Threadlinqs vulnerability feed.

Affected products and versions

Aquasec: Setup-trivy, Trivy 0.69.4, Trivy Action
Litellm: Litellm 1.82.7, Litellm 1.82.8
Telnyx: Telnyx 4.87.1, Telnyx 4.87.2

How to fix CVE-2026-33634

Vendor advisory: https://github.com/aquasecurity/trivy/discussions/10425. Because CVE-2026-33634 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2026-04-09. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-33634

4 tracked threats in the Threadlinqs corpus reference CVE-2026-33634, either in the campaign’s CVE list or as an indicator on the campaign record.

TeamPCP LiteLLM Supply Chain Attack — Trojaned PyPI Packages (v1.82.7/1.82.8) with Multi-Stage C2 Payload — CRITICAL · 2026-03-31
TeamPCP Supply Chain Attack on LiteLLM — Trojanized PyPI Packages with .pth Persistence and Multi-Stage Credential Stealer — CRITICAL · 2026-03-25
TeamPCP Supply Chain Campaign: LiteLLM PyPI Compromise, CanisterWorm npm Propagation, and Multi-Ecosystem Attack (CVE-2026-33634) — CRITICAL · 2026-03-24
Trivy Supply Chain Compromise — TeamPCP Credential-Stealing Malware Injected into CI/CD Pipelines (CVE-2026-33634) — CRITICAL · 2026-03-24

Sources

Seeded from threat-derived and not yet processed by the Threadlinqs enrichment pipeline, so blank CVSS, EPSS or KEV fields above mean NOT MEASURED rather than measured-absent.

Full detection coverage & IOCs for threats exploiting CVE-2026-33634 are available via the Threadlinqs MCP server (Purple tier). View plans →

← all vulnerabilities · Markdown version · Threadlinqs Intelligence