CVE Intelligence
CISA KEV High exploit reference

CVE-2026-33634 — Aquasecurity Trivy Embedded Malicious Code Vulnerability

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.

Published Mar 23, 2026 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · Mar 26, 2026 ☠ TeamPCP Proofs of concept on GitHub · 5
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Exploited by 1 threat actor(s) (MITRE ATT&CK)+10
  • Public exploit/PoC (github)+6
  • EPSS 1.7% (30-day exploitation probability)+11
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Mar 26, 2026
EPSS FIRST
1.68%
ahead of 77% of scored CVEs · Oct 14, 2026
Affects
Aquasec
Setup-trivy and 8 more
CVSS base
8.8
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented mitigation — github.com (NIST National Vulnerability Database)
  • Documented mitigation — github.com (NIST National Vulnerability Database)
  • Documented mitigation — github.com (NIST National Vulnerability Database)
  • Actions Aquasecurity/trivy-action: fixed in version 0.35.0 — github.com (GitHub Security Advisories)
  • Actions Aquasecurity/setup-trivy: fixed in version 0.2.6 — github.com (GitHub Security Advisories)

CISA required action 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.

US federal deadline: Apr 9, 2026 — passed 189 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Aquasec Setup-trivy, Aquasec Trivy, Aquasec Trivy Action…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Aquasec Setup-trivy < 0.2.6 Vulnerable NIST National Vulnerability Database
Aquasec Trivy version 0.69.4 Vulnerable NIST National Vulnerability Database
Aquasec Trivy Action < 0.35.0 Vulnerable NIST National Vulnerability Database
Aquasecurity Setup-trivy version < 0.2.6 Vulnerable CVE Program (cve.org) e CISA ADP
Aquasecurity Trivy version = 0.69.4 Vulnerable CVE Program (cve.org) e CISA ADP
Aquasecurity Trivy-action version < 0.35.0 Vulnerable CVE Program (cve.org) e CISA ADP
BerriAI Litellm version >= 1.82.7, <= 1.82.8 Vulnerable CVE Program (cve.org) e CISA ADP
Litellm Litellm version 1.82.7version 1.82.8 Vulnerable NIST National Vulnerability Database
Team-telnyx Telnyx version >= 4.87.1, <= 4.87.2 Vulnerable CVE Program (cve.org) e CISA ADP
Telnyx Telnyx version 4.87.1version 4.87.2 Vulnerable NIST National Vulnerability Database
Actions Aquasecurity/setup-trivy < 0.2.6 Vulnerable GitHub Security Advisories
Actions Aquasecurity/trivy-action < 0.35.0 Vulnerable GitHub Security Advisories
Go Github.com/aquasecurity/trivy version 0.69.4 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.4 CVSS 4.0 Critical — — security-advisories@github.com via NIST National Vulnerability Database
9.4 CVSS 4.0 Critical — — GitHub_M via CVE Program (cve.org) e CISA ADP
8.8 CVSS 3.1 High 2.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-506

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Mar 26, 2026
Federal deadline
Apr 9, 2026
passed 189 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Proofs of concept on GitHub

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

Threat actors exploiting this CVE MITRE ATT&CK

According to MITRE ATT&CK.

TeamPCP G1056

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 1.68%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Hunt retroactively in logs from before Mar 26, 2026 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 13, 2026 · GitHub Security Advisories
  • Affected products added · go/github.com/aquasecurity/trivy, actions/aquasecurity/trivy-action, actions/aquasecurity/setup-trivy
    Oct 13, 2026 · GitHub Security Advisories
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · aquasec/setup-trivy, aquasec/trivy, aquasec/trivy action, litellm/litellm, telnyx/telnyx
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.4 → 8.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 13, 2026
  • Affected products added · aquasecurity/setup-trivy, aquasecurity/trivy-action, aquasecurity/trivy, berriai/litellm, team-telnyx/telnyx
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • CVSS changed · 9.4
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Added to CISA KEV catalog
    Mar 25, 2026 · CISA
  • CVE published
    Mar 23, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 3× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

17 on the record

Elsewhere on this site

Aquasec
every CVE for this vendor
2026-03
what else CISA listed that month
CWE-506
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-108575 BerriAI LiteLLM Secret Resolution main.py get_secret improper authorization 4d
  • CVE-2026-108574 BerriAI LiteLLM Spend Tracking spend_management_endpoints.py ui_view_session_spend_logs authorization 4d
  • CVE-2026-84377 LiteLLM: Authenticated SSRF and provider-credential exfiltration via unvalidated request-body routing parameters Sep 2, 2026
  • CVE-2026-63328 Trivy: Path Traversal in Trivy Plugin Manager Allows Arbitrary File Write Aug 18, 2026
  • CVE-2026-59819 LiteLLM: Local file read via request-supplied OIDC file references Jul 8, 2026
  • CVE-2026-59822 BerriAI LiteLLM Improper Authentication Vulnerability KEV Jul 8, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-33634 is "Aquasecurity Trivy Embedded Malicious Code Vulnerability", rated High. It affects Setup-trivy (Aquasec); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.8 describes technical severity. EPSS 1.68% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.