Aquasecurity setup-trivy
Trivy ecosystem supply chain briefly compromised
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.2.6
Fixed in 0.2.6
- < 0.35.0
Fixed in 0.35.0
- = 0.69.4
- >= 1.82.7, <= 1.82.8
- >= 4.87.1, <= 4.87.2
Mitigation
Upgrade setup-trivy to 0.2.6 or later.
Upgrade trivy-action to 0.35.0 or later.
References
- Vendor advisory github.com/aquasecurity/trivy/security/advisor…
- Vendor advisory github.com/team-telnyx/telnyx-python/security/…
Timeline
Days relative to CVE publicationFirst public PoC 6.7 days after publication; added to CISA KEV 3 days after publication. First PoC: fevar54/CVE-2026-33634-Scanner (created 30 Mar 2026, found by us: backfilled).
PoC repositories
Found on GitHub.2 PoCs · 1 pending · 1 informational · 1 not a PoC · 1 suspicious or fake
PoCs 2
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| fevar54/CVE-2026-33634-Scanner | 30 Mar 2026 +6.7 d | 0 | Scanner |
| joaovicdev/EXPLOIT-CVE-2026-33634 | 21 Sep 2026 +182 d | 0 | PoC |
Pending 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| dfs333/trivysupplychainanalysis | 15 Jul 2026 +113 d | 1 | Pending · repository exceeds size limit |
Informational 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| ugurrates/teampcp-supply-chain-attack | 25 Mar 2026 +1.1 d | 12 | Informational · detection |
Not a PoC 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| AshleyT3/docker-socket-risk-demos | 31 Mar 2026 +7.5 d | 0 | Not a PoC · unrelated
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Suspicious or fake 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| yfolias/trivy-compromise-poc | 7 Apr 2026 +14 d | 0 | Fake |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| CVE record (tagged exploit) | https://rosesecurity.dev/2026/03/20/typosquatting-trivy.html | unknown | 14 Nov 2026 |
PoC characteristics
What to hunt for in your logs · from 2 PoC reposGET /loot
- Ports
- 4000, 8080, 9000, 9100
- Seen in
- 1 repo: joaovicdev/EXPLOIT-CVE-2026-33634
- Evidence
- joaovicdev/EXPLOIT-CVE-2026-33634/README.md:104 joaovicdev/EXPLOIT-CVE-2026-33634/exploit/exploit.py:122
GET /v1/models
- Ports
- 4000, 8080, 9000, 9100
- Seen in
- 1 repo: joaovicdev/EXPLOIT-CVE-2026-33634
- Evidence
- joaovicdev/EXPLOIT-CVE-2026-33634/exploit/exploit.py:138
POST /v1/chat/completions
- Body markers
"model":"gpt-4o""api_base":"http://internal.lab:9000/admin/keys""messages""api_base":"http://imds.lab/latest/meta-data/iam/security-credentials/litellm-gateway-role""model""api_base"inapplication/json- Ports
- 4000, 8080, 9000, 9100
- Seen in
- 1 repo: joaovicdev/EXPLOIT-CVE-2026-33634
- Evidence
- joaovicdev/EXPLOIT-CVE-2026-33634/README.md:111 joaovicdev/EXPLOIT-CVE-2026-33634/README.md:117 joaovicdev/EXPLOIT-CVE-2026-33634/exploit/exploit.py:109
Regex
Generated from PoC characteristics; not yet reviewed. Matches the request path and query.
(?i)^/loot(?:[?#].*)?$
(?i)^/v1/models(?:[?#].*)?$
(?i)^/v1/chat/completions(?:[?#].*)?$
Suricata
Template generated from PoC characteristics. Review before deploying.
alert http any any -> $HOME_NET [4000,8080,9000,9100] (msg:"GG PoC-Monitor CVE-2026-33634 aquasecurity setup-trivy exploit attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/loot"; reference:url,poc.griffinguard.io/cve/CVE-2026-33634; classtype:web-application-attack; sid:9121129; rev:1;)
alert http any any -> $HOME_NET [4000,8080,9000,9100] (msg:"GG PoC-Monitor CVE-2026-33634 aquasecurity setup-trivy exploit attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/v1/models"; reference:url,poc.griffinguard.io/cve/CVE-2026-33634; classtype:web-application-attack; sid:9415609; rev:1;)
alert http any any -> $HOME_NET [4000,8080,9000,9100] (msg:"GG PoC-Monitor CVE-2026-33634 aquasecurity setup-trivy exploit attempt"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/v1/chat/completions"; http.request_body; content:"|22|model|22|:|22|gpt-4o|22|"; http.request_body; content:"|22|api_base|22|:|22|http://internal.lab:9000/admin/keys|22|"; http.request_body; content:"|22|messages|22|"; http.request_body; content:"|22|api_base|22|:|22|http://imds.lab/latest/meta-data/iam/security-credentials/litellm-gateway-role|22|"; http.request_body; content:"|22|model|22|"; http.request_body; content:"|22|api_base|22|"; reference:url,poc.griffinguard.io/cve/CVE-2026-33634; classtype:web-application-attack; sid:9821607; rev:1;)
Sigma
Template generated from PoC characteristics. Review before deploying.
title: aquasecurity setup-trivy exploit attempt (CVE-2026-33634)
id: gg-pocmon-cve-2026-33634-9121129
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-33634. Generated, not reviewed.
references:
- https://poc.griffinguard.io/cve/CVE-2026-33634
logsource:
category: webserver
detection:
selection:
cs-method: GET
cs-uri-stem|contains|all:
- '/loot'
condition: selection
falsepositives:
- Authorized vulnerability scanning
level: critical
tags:
- attack.initial_access
- attack.t1190
- cve.2026.33634
title: aquasecurity setup-trivy exploit attempt (CVE-2026-33634)
id: gg-pocmon-cve-2026-33634-9415609
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-33634. Generated, not reviewed.
references:
- https://poc.griffinguard.io/cve/CVE-2026-33634
logsource:
category: webserver
detection:
selection:
cs-method: GET
cs-uri-stem|contains|all:
- '/v1/models'
condition: selection
falsepositives:
- Authorized vulnerability scanning
level: critical
tags:
- attack.initial_access
- attack.t1190
- cve.2026.33634
title: aquasecurity setup-trivy exploit attempt (CVE-2026-33634)
id: gg-pocmon-cve-2026-33634-9821607
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-33634. Generated, not reviewed.
references:
- https://poc.griffinguard.io/cve/CVE-2026-33634
logsource:
category: webserver
detection:
selection:
cs-method: POST
cs-uri-stem|contains|all:
- '/v1/chat/completions'
condition: selection
falsepositives:
- Authorized vulnerability scanning
level: critical
tags:
- attack.initial_access
- attack.t1190
- cve.2026.33634