As of , CVE-2026-33634 in Aquasecurity Trivy is on CISA's list of exploited vulnerabilities: CISA listed it on . Our patch-first group: Patch this week.
CVE-2026-33634
Aquasecurity Trivy: Embedded Malicious Code. Exploited, and in our Patch this week group.
Our patch-first group
Patch this week
- EPSS 0.62
CISA's 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.
Patch infofixed versions and vendor advice
What to install
Affects aquasecurity setup-trivy before 0.2.6.
Fixed in 0.2.6.
Affects aquasecurity trivy-action before 0.35.0.
Fixed in 0.35.0.
Affects aquasecurity trivy 0.69.4.
The record's list of affected products names no fixed version.
Affects BerriAI LiteLLM from 1.82.7 up to and including 1.82.8.
The record's list of affected products names no fixed version.
Affects telnyx from 4.87.1 up to and including 4.87.2.
The record's list of affected products names no fixed version.
Vendor advice
Vendor advice: github.com, from CISA's entry.
- github.comThis vulnerability involves a supply‐chain compromise in a product that may be used across multiple products and environments. Additional…
- EPSS score
- 0.62Higher than 99% of the CVEs EPSS scores.
EPSS estimates the chance of exploitation activity in the next 30 days.
- Exploited
- Yes CISA listed it on 26 March 2026
- US federal deadline
- 9 April 2026 14 days after CISA listed it. US federal civilian agencies must fix it by then.
- Used in ransomware campaigns
- Not known to CISA
- EPSS when listed
- 0.00 on 26 March 2026 EPSS on the day CISA listed it.
- Public exploit
- None found Neither Metasploit nor Exploit-DB lists one.
In software packages
Affected packages
Software packages that the advisories for this CVE name. Each line is what one advisory says, with its id.
github.com/aquasecurity/trivyGo
Affects github.com/aquasecurity/trivy 0.69.4.
The advisory names no fixed version.
Advisory GHSA-69fq-xp46-6x23github.com/aquasecurity/trivyGo
Affects github.com/aquasecurity/trivy from 0.69.4 before 0.70.0.
Fixed in 0.70.0.
Advisory GO-2026-4919
Since listing
EPSS since listing
EPSS for CVE-2026-33634 since CISA listed it, on the days its value to 2 decimals changed. EPSS scores by FIRST.
Show the numbers
| From | EPSS |
|---|---|
| 0.00 | |
| 0.27 | |
| 0.21 | |
| 0.17 | |
| 0.15 | |
| 0.17 | |
| 0.15 | |
| 0.17 | |
| 0.16 | |
| 0.18 | |
| 0.33 | |
| 0.27 | |
| 0.29 | |
| 0.24 | |
| 0.27 | |
| 0.60 | |
| 0.59 | |
| 0.02 | |
| 0.60 | |
| 0.62 |
Timeline
What happened when
- The CVE record was published.
- CISA added it to its list of exploited vulnerabilities.
- The US federal deadline to fix it.
CISA's required action
What CISA says to do
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Read further: CISA's catalog
The flaw
What the flaw 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's 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.
The CVE record's description, from GitHub_M, shortened; full text on cve.org
- CVE published
- 23 March 2026
- Assigned by
- GitHub_M
- CVSS
- 9.4 Critical (CVSS 4.0, from the CNA)
- CWE-506
- Embedded Malicious Code
- CISA SSVC, exploitation
- active
- CISA SSVC, automatable
- no
- CISA SSVC, technical impact
- total
Sources
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
- CWE names: Copyright © 2006-2026, The MITRE Corporation. CWE, CWSS, CWRAF, and the CWE logo are trademarks of The MITRE Corporation (source). Licence: CWE Terms of Use
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)
- Package advisories from the GitHub Advisory Database (CC BY 4.0). Version ranges are reworded as sentences (source). Licence: CC BY 4.0
- Package advisories from the Go vulnerability database (CC BY 4.0). Version ranges are reworded as sentences (source). Licence: CC BY 4.0