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

In short

Aquasecurity Trivy has a weakness classified as embedded malicious code (CWE-506). CISA added it to its Known Exploited Vulnerabilities catalog on 2026-03-26. NVD lists CVSS 4.0 at 9.4 CRITICAL.

What it is

“Aquasecurity Trivy contains an embedded malicious code vulnerability that could allow an attacker to gain access to everything in the CI/CD environment, including all tokens, SSH keys, cloud credentials, database passwords, and any sensitive configuration in memory.” — CISA KEV, retrieved 2026-11-01

“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.” — NVD, retrieved 2026-11-01

Who is affected

Aquasecurity Trivy. NVD lists the following versions as affected:

• Aquasec setup-trivy: before 0.2.6
• Aquasec Trivy: version 0.69.4
• Aquasec Trivy Action: before 0.35.0
• Litellm Litellm: version 1.82.7
• Litellm Litellm: version 1.82.8
• Telnyx Telnyx: version 4.87.1
• Telnyx Telnyx: version 4.87.2

Exploitation status

CISA KEV added: 2026-03-26. Known ransomware campaign use: Not reported by CISA. Due date CISA set for US federal civilian agencies: 2026-04-09.

Scores

NVD CVSS 4.0: 9.4 CRITICAL; vector 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; source [email protected].

EPSS by FIRST: 59.73%; percentile 99.13; score date 2026-10-31. EPSS estimates the probability of exploitation in the next 30 days.

CWE: CWE-506.

Timeline

CISA 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.” — CISA KEV

What to do

• Confirm whether you run Aquasecurity Trivy and which version.
• Apply the vendor update or mitigation in the advisory.
• Follow CISA’s required action.
• Review the vendor guidance on signs of compromise.
• Track the fix through completion.

References

• Third Party Advisory: https://docs.litellm.ai/blog/security-update-march-2026
• Third Party Advisory: https://futuresearch.ai/blog/litellm-pypi-supply-chain-attack
• Issue Tracking, Mitigation, Third Party Advisory: https://github.com/BerriAI/litellm/issues/24518
• Issue Tracking, Vendor Advisory: https://github.com/aquasecurity/trivy/discussions/10425
• Third Party Advisory: https://github.com/pypa/advisory-database/tree/main/vulns/litellm/PYSEC-2026-2.yaml
• Third Party Advisory: https://github.com/team-telnyx/telnyx-python/security/advisories/GHSA-955r-262c-33jc
• Issue Tracking, Mitigation, Third Party Advisory: https://github.com/BerriAI/litellm/issues/24518#issuecomment-4127436387
• NVD detail
• CVE.org record
• CISA KEV catalog

Sources and dates

CISA Known Exploited Vulnerabilities Catalog, version 2026.10.30; retrieved 2026-11-01. CISA KEV data: CC0 1.0. No endorsement by CISA.

NVD retrieved: 2026-11-01. This product uses the NVD API but is not endorsed or certified by the NVD.

EPSS scores by FIRST; score date 2026-10-31.