CVE-2026-33634

Published Mar 23, 2026

Last updated 7 months ago

Exploit known CVSS critical 9.4

npm

Docker

Ubuntu

Cloud

Zero-day

Container Security

Supply chain

Overview

Description: 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.
Source: security-advisories@github.com
NVD status: Analyzed
Products: setup-trivy, trivy, trivy_action, litellm, telnyx

Risk scores

CVSS 4.0

Type: Secondary
Base score: 9.4
Impact score: -
Exploitability score: -
Vector string: 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Severity: CRITICAL

CVSS 3.1

Type: Primary
Base score: 8.8
Impact score: 5.9
Exploitability score: 2.8
Vector string: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Severity: HIGH

Known exploits

Data from CISA

Vulnerability name: Aquasecurity Trivy Embedded Malicious Code Vulnerability
Exploit added on: Mar 26, 2026
Exploit action due: Apr 9, 2026
Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Weaknesses

security-advisories@github.com: CWE-506

Hype score: Not currently trending

Configurations

[
  {
    "nodes": [
      {
        "cpeMatch": [
          {
            "criteria": "cpe:2.3:a:aquasec:setup-trivy:*:*:*:*:*:*:*:*",
            "matchCriteriaId": "1F71EEF3-BE0B-4465-8FA9-6F7AC0232611",
            "versionEndExcluding": "0.2.6",
            "vulnerable": true
          },
          {
            "criteria": "cpe:2.3:a:aquasec:trivy:0.69.4:*:*:*:*:go:*:*",
            "matchCriteriaId": "0FA4DA16-3603-489F-B55B-758F0C90FA7D",
            "vulnerable": true
          },
          {
            "criteria": "cpe:2.3:a:aquasec:trivy_action:*:*:*:*:*:*:*:*",
            "matchCriteriaId": "B248C8E0-CFEF-484E-BA95-95E56B0EF550",
            "versionEndExcluding": "0.35.0",
            "vulnerable": true
          }
        ],
        "negate": false,
        "operator": "OR"
      }
    ]
  },
  {
    "nodes": [
      {
        "cpeMatch": [
          {
            "criteria": "cpe:2.3:a:litellm:litellm:1.82.7:*:*:*:*:*:*:*",
            "matchCriteriaId": "754B1179-4A04-46A0-87EA-BAE142088E23",
            "vulnerable": true
          },
          {
            "criteria": "cpe:2.3:a:litellm:litellm:1.82.8:*:*:*:*:*:*:*",
            "matchCriteriaId": "AE8FD26B-9DD9-4BC4-A15F-01852A979B79",
            "vulnerable": true
          }
        ],
        "negate": false,
        "operator": "OR"
      }
    ]
  },
  {
    "nodes": [
      {
        "cpeMatch": [
          {
            "criteria": "cpe:2.3:a:telnyx:telnyx:4.87.1:*:*:*:*:python:*:*",
            "matchCriteriaId": "3F64D45B-84AA-433F-A29E-09A1F957B2E4",
            "vulnerable": true
          },
          {
            "criteria": "cpe:2.3:a:telnyx:telnyx:4.87.2:*:*:*:*:python:*:*",
            "matchCriteriaId": "C5216D3E-B5AD-48A8-B7C9-6DD16981ECAD",
            "vulnerable": true
          }
        ],
        "negate": false,
        "operator": "OR"
      }
    ]
  }
]

References

Sources include official advisories and independent security research.

Overview

Risk scores

CVSS 4.0

CVSS 3.1

Known exploits

Weaknesses

Social media

Configurations

Related CVEs

References