CVE-2026-33634
Published: 23 March 2026
Summary
CVE-2026-33634 is a high-severity Embedded Malicious Code (CWE-506) vulnerability in Litellm Litellm. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Compromise Software Supply Chain (T1195.002); ranked in the top 5.2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified are NIST 800-53 SI-7 (Software, Firmware, and Information Integrity) and SR-11 (Component Authenticity).
Threat & Defense at a Glance
Threat & Defense Details
Mitigating Controls (NIST 800-53 r5)AI
Requires verification of component authenticity prior to use, directly preventing integration of malicious Trivy releases and force-pushed GitHub Action tags into CI/CD pipelines.
Mandates integrity checks such as commit SHA pinning for Trivy software and actions, blocking tampered versions from execution.
Establishes secure authenticator management and rotation procedures to mitigate credential exfiltration during non-atomic rotations and post-compromise secret theft.
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
CVE describes supply chain compromise of Trivy release (T1195.002), tampering with GitHub Actions as development tools (T1195.001), and execution of credential-stealing malware in CI/CD pipelines (T1677).
NVD 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`…
more
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.
Deeper analysisAI
CVE-2026-33634 is a supply chain compromise affecting Trivy, an open-source security scanner, stemming from a threat actor's use of compromised credentials to publish a malicious Trivy version 0.69.4 release on March 19, 2026. The attack also involved force-pushing 76 of 77 version tags in the aquasecurity/trivy-action GitHub Action (versions 0.0.1 through 0.34.2) to credential-stealing malware and replacing all 7 tags in the aquasecurity/setup-trivy GitHub Action (versions 0.2.0 through 0.2.6, prior to recreation of 0.2.6 with a safe commit). This incident continues a supply chain attack that began in late February 2026, exacerbated by non-atomic credential rotation after an initial March 1 disclosure, allowing the attacker to exfiltrate newly rotated secrets. Affected components include the aquasecurity/trivy Go binary and container image at version 0.69.4.
Users integrating the affected Trivy components into CI/CD pipelines, particularly those referencing version tags rather than commit SHAs in GitHub Actions workflows, could unwittingly execute the credential-stealing malware. An attacker with low-privilege access (PR:L) could exploit this over the network (AV:N) with low complexity (AC:L) and no user interaction (UI:N), achieving high confidentiality, integrity, and availability impacts (CVSS 8.8). Exploitation enables theft of secrets accessible to the compromised pipelines, with a fallback exfiltration mechanism potentially creating a repository named tpcp-docs in the victim's GitHub organization as an indicator of successful compromise.
Advisories recommend immediate rotation of all secrets accessible to affected pipelines if there's any chance a compromised version was pulled or executed, removal of affected artifacts, and review of workflows using aquasecurity/trivy-action or aquasecurity/setup-trivy. Organizations should verify whether Trivy v0.69.4 was obtained from any source, check workflow run logs from March 19–20, 2026 for signs of compromise if version tags were used, and pin GitHub Actions to full, immutable commit SHA hashes instead of mutable tags. Known safe versions include Trivy 0.69.2 and 0.69.3, trivy-action 0.35.0, and setup-trivy 0.2.6 (recreated).
This vulnerability saw real-world exploitation on March 19, 2026, as part of an ongoing supply chain campaign, with detailed discussions available in Aquasecurity's GitHub advisories and related security notices.
Details
- CWE(s)
- KEV Date Added
- 26 March 2026