chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - #145

Open
renovate[bot] wants to merge 1 commit into
devfrom
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Open

chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]#145
renovate[bot] wants to merge 1 commit into
devfrom
renovate/github-tags-aquasecurity-trivy-action-vulnerability

Conversation

@renovate

@renovaterenovateBot commented Mar 24, 2026•
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

PackageTypeUpdateChange
aquasecurity/trivy-actionactionminor0.33.1 → 0.35.0

Trivy Action has a script injection via sourced env file in composite action

CVE-2026-26189 / GHSA-9p44-j4g5-cfx5

More information

Details

Command Injection in aquasecurity/trivy-action via Unsanitized Environment Variable Export

A command injection vulnerability exists in aquasecurity/trivy-action due to improper handling of action inputs when exporting environment variables. The action writes export VAR=<input> lines to trivy_envs.txt based on user-supplied inputs and subsequently sources this file in entrypoint.sh.

Because input values are written without appropriate shell escaping, attacker-controlled input containing shell metacharacters (e.g., $(...), backticks, or other command substitution syntax) may be evaluated during the sourcing process. This can result in arbitrary command execution within the GitHub Actions runner context.

Severity:

Moderate

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

CWE-78: Improper Neutralization of Special Elements used in an OS Command (‘OS Command Injection’)

Impact:

Successful exploitation may lead to arbitrary command execution in the CI runner environment.

Affected Versions:

  • Versions >= 0.31.0 and <= 0.33.1
  • Introduced in commit 7aca5ac

Affected Conditions:

The vulnerability is exploitable when a consuming workflow passes attacker-controlled data into any action input that is written to trivy_envs.txt. Access to user input is required by the malicious actor.

A representative exploitation pattern involves incorporating untrusted pull request metadata into an action parameter. For example:

- uses: aquasecurity/trivy-action@0.33.1with:
output: "trivy-$.sarif"

If the pull request title contains shell syntax, it may be executed when the generated environment file is sourced.

Not Affected:

  • Workflows that do not pass attacker-controlled data into trivy-action inputs
  • Workflows that upgrade to a patched version that properly escapes shell values or eliminates the source ./trivy_envs.txt pattern
  • Workflows where user input is not accessible.

Call Sites:

  • action.yaml:188 — set_env_var_if_provided writes unescaped export lines
  • entrypoint.sh:9 — sources ./trivy_envs.txt

Severity

  • CVSS Score: 5.9 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Trivy ecosystem supply chain was briefly compromised

CVE-2026-33634 / GHSA-69fq-xp46-6x23

More information

Details

Summary

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.
On March 22, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.5 and v0.69.6 DockerHub images.

Exposure Window
ComponentStart (UTC)End (UTC)Duration
trivy v0.69.42026-03-19 18:22 12026-03-19 ~21:42~3 hours
trivy-action2026-03-19 ~17:43 22026-03-20 ~05:40~12 hours
setup-trivy2026-03-19 ~17:43 22026-03-19 ~21:44~4 hours
dockerhub trivy images v0.69.5 and v0.69.62026-03-22 15:432026-03-23 ~01:40~10 hours
Affected Components

Note that all malicious components, artifacts, commits, etc have been removed from all sources and destinations (yet they may linger in intermediary caches). Use this information to understand if you have been exposed to the malicious artifacts during the exposure window.

trivy binary and image

You are affected if you used:

  1. trivy binaries version v0.69.4 (or latest during the exposure window) distributed via GitHub, Deb, RPM.
  2. trivy container images v0.69.4 (or latest during the exposure window) distributed via GHCR, ECR public, Docker Hub.
  3. trivy container images v0.69.5 and v0.69.6 (or latest during the exposure window) distributed via Docker Hub.

You are not affected if you used:

  1. trivy (binary or image) version v0.69.3 or earlier.
    1. v0.69.3 is protected by GitHub's immutable releases feature (enabled March 3, before v0.69.3 was published).
    2. v0.69.2 predates immutable releases enablement but integrity can be verified via sigstore signatures (see "How to Verify" section below).
  2. trivy images referenced by digest.
  3. trivy binaries built from source.
    1. The malicious code was not committed to Trivy's main branch. It was fetched and built on the ephemeral runner, and also committed to a v0.70.0 branch but no release or git tag was ever pushed.
  4. homebrew from official formula (brew install trivy)
    1. The official homebrew formula is building trivy directly from source.
    2. There's an additional custom trivy tap which was compromised as part of the v0.69.4 release, but that tap requires special installation and is not even mentioned in the trivy documentation.
aquasecurity/trivy-action GitHub Action

You are affected if you used:

  1. Any tags prior except 0.35.0 (0.0.1 – 0.34.2) to reference the action.
  2. the action's version: latest parameter explicitly (not the default) during the trivy binary exposure window.
  3. SHA pinning to a commit prior to 2025-04-09.
    1. trivy-action started pinning setup-go with pull request trivy-action#456. If you pinned trivy-action to a commit prior to that PR (merged 2025-04-09), then you would get a safe trivy-action but it would get a malicious setup-trivy, if invoked during the setup-trivy exposure window.

You are not affected if you used:

  1. 0.35.0 tag
    1. 0.35.0 is protected by GitHub's immutable releases feature (enabled March 4, before 0.35.0 was published) and was not affected by the tag hijacking attack.
  2. SHA pinning to a safe commit commit after 2025-04-09.
aquasecurity/setup-trivy GitHub Action

You are affected if you used:

  1. Any version without pinning.

You are not affected if you used:

  1. SHA pinning to a safe commit.
Attack Details
Root Cause

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.

Trivy v0.69.4 binary and container images

The attacker created a malicious release by:

  1. Pushing a commit (1885610c) that swapped the actions/checkout reference to an imposter commit (70379aad) containing a composite action that downloaded malicious Go source files from a typosquatted domain
  2. Adding --skip=validate to goreleaser to bypass binary validation
  3. Tagging this commit as v0.69.4, triggering the release pipeline

The compromised release was distributed across Trivy's regular distribution channels channels: GHCR, ECR Public, Docker Hub (both 0.69.4 and latest tags), deb/rpm packages, and get.trivy.dev.

The attacker attempted to release a v0.70.0 malicious release but that was stopped prematurely.

trivy-action tag hijacking

The attacker force-pushed 76 of 77 version tags to malicious commits that injected an infostealer into entrypoint.sh. The malicious code executes before the legitimate Trivy scan and does the following:

  1. Dumps Runner.Worker process memory via /proc/<pid>/mem to extract secrets. Sweeps 50+ filesystem paths for SSH keys, AWS/GCP/Azure credentials, Kubernetes tokens, Docker configs, .env files, database credentials, and cryptocurrency wallets.
  2. Encrypts collected data using AES-256-CBC with RSA-4096 hybrid encryption.
  3. Transmits to attacker-controlled infrastructure. If exfiltration fails and INPUT_GITHUB_PAT is set, creates a public tpcp-docs repository on the victim's GitHub account and uploads stolen data as a release asset.
setup-trivy release replacement

All 7 existing tags (v0.2.0 – v0.2.6) were force-pushed to malicious commits. The malicious action.yaml contained the same infostealer as trivy-action, injected as a "Setup environment" step that executes before the legitimate Trivy installation.
We have removed all malicious releases within ~4 hours and re-created v0.2.6 with safe content. Tags v0.2.0 – v0.2.5 were not restored.

Trivy v0.69.5 and v0.69.6 docker image published.

The attacker created aquasec/trivy:0.69.5 and aquasec/trivy:0.69.6 with the same C2 domain as the v0.69.4 payload, and pushed them directly to Docker Hub using separately-compromised Docker Hub credentials (not via GitHub). No corresponding GitHub tags or releases existed.
We have removed all tags related to 0.69.5 and 0.69.6 and restored the latest tag to the safe 0.69.3 tag.

Recommended Actions
Update to Known-Safe Versions
ComponentSafe Version
Trivy binaryv0.69.2, v0.69.3
trivy-actionv0.35.0
setup-trivyv0.2.6

Regarding trivy-action: The original tags (0.0.1 – 0.34.2) were deleted during remediation. Because the attacker's force-push caused these tags to be treated as immutable releases by GitHub, they cannot be re-created with the same names. New tags have been published with a v prefix (v0.0.1 – v0.34.2) pointing to the original legitimate commits. Three tags: v0.0.10, v0.34.1, and v0.34.2 have not yet been restored. If you need to reference a version older than 0.35.0, use the v-prefixed tag (e.g., aquasecurity/trivy-action@v0.34.0 instead of @0.34.0).

Rotate All Potentially Exposed Secrets

Based on information shared above, if there is any possibility that a compromised version ran in your environment, all secrets accessible to affected pipelines must be treated as exposed and rotated immediately.

Audit Trivy Versions

Check whether your organization pulled or executed Trivy v0.69.4 from any source. Remove any affected artifacts immediately.

Audit GitHub Action References

Review all workflows using aquasecurity/trivy-action or aquasecurity/setup-trivy. Check workflow run logs from March 19–20, 2026 for signs of compromise.

Search for Exfiltration Artifacts

Look for repositories named tpcp-docs in your 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 SHA Hashes

Pin GitHub Actions to full, immutable commit SHA hashes, don't use mutable version tags. As described here: https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions

How to Verify Existing Installations
Binary verification
##### Download binary and sigstore bundle
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz"
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json"##### Verify signature
$ cosign verify-blob \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--bundle trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json \
trivy_0.69.2_Linux-64bit.tar.gz
Verified OK
##### Check signing timestamp
$ date -u -d @$(jq -r '.verificationMaterial.tlogEntries[].integratedTime' trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json)
Sat Mar 1 19:11:02 UTC 2026
##### ✅ Signed on Mar 1, before the attack on Mar 19
Container image verification
##### Verify signature and get image digest
$ cosign verify \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--new-bundle-format \
ghcr.io/aquasecurity/trivy:0.69.2
Verification for ghcr.io/aquasecurity/trivy:0.69.2 --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The code-signing certificate was verified using trusted certificate authority certificates
##### Get digest and check all signing timestamps via Rekor
$ DIGEST=$(cosign verify \ --certificate-identity-regexp 'https://github\.com/aquasecurity/' \ --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \ --new-bundle-format -o json ghcr.io/aquasecurity/trivy:0.69.2 2>/dev/null | \ jq -r '.[0].critical.image."docker-manifest-digest"')
$ rekor-cli search --sha "$DIGEST"| grep -v 'Found'|whileread uuid;do
rekor-cli get --uuid "$uuid"| grep IntegratedTime
done
IntegratedTime: 2026-03-01T19:13:52Z
IntegratedTime: 2026-03-01T19:13:47Z
IntegratedTime: 2026-03-01T19:13:57Z
IntegratedTime: 2026-03-01T19:13:54Z
IntegratedTime: 2026-03-01T19:13:46Z
IntegratedTime: 2026-03-01T19:13:37Z
##### ✅ All signed on Mar 1, before the attack on Mar 19
Indicators of Compromise
Executable binaries
SHA256Filename
c5b16c42dbd2a1494141cd651a406ec9094d5031a421c0aa624c4d139ae81239trivy_0.69.4_FreeBSD_64bit.tar.gz
cff74e3e9ac0cda2078d31800d8fcad832d7b52c9920b085054d1e96dacff8a3trivy_0.69.4_Linux-32bit.deb
55047c55a5ceab6d80b13884b4a4e8cd27a0bab7a218a952a00aae9e05f16f80trivy_0.69.4_Linux-32bit.rpm
ba04ba6a0c028cde17599c8ddaefdb854055c5a23c595e06630732002ea59a76trivy_0.69.4_Linux-32bit.tar.gz
0ca60dd18178d1c79d59cc06be12c540c121a4aea467484244667131aa13c311trivy_0.69.4_Linux-64bit.deb
a5696321a6c93071f46c8bb8cbd0a8d2bce6d1860cc3c109247a4e8b64ebd317trivy_0.69.4_Linux-64bit.rpm
385d498d18a3a7c67878ca7322716f9da25683eb1a4bf9e9592da0d5f2ab09f6trivy_0.69.4_Linux-64bit.tar.gz
8f0c7b92b251c61cbca2add06c676dd21fde8fbb2d0cd6616383fae29b21756atrivy_0.69.4_Linux-ARM.deb
c5df9d1bc6275711b2884a9ed4aacfe4e10dbe3c8f6c79df59126fd0e6dcd83ftrivy_0.69.4_Linux-ARM.rpm
f7a9bbfec8add36c548add4d875848b8b57c21fabe236d115f1c49113d12b332trivy_0.69.4_Linux-ARM.tar.gz
9a833d68a49ec6d44bc50fb9ff3b184bafb0edc913e1293daebe51d334676a70trivy_0.69.4_Linux-ARM64.deb
451ce0c4deb620894d07a2f4a37c8ea3b7a4f9b6d111651b4ac3bcc737b0fac0trivy_0.69.4_Linux-ARM64.rpm
e401ae1e6d2442fa9a0c79dc0f3b0457ecfebf74a9c0a920159c49437f663aeftrivy_0.69.4_Linux-ARM64.tar.gz
284622577cf6a7c58704de60194205f765fcef432934c200b462ef0290aa5f57trivy_0.69.4_Linux-PPC64LE.deb
5fac89e66d70cadec5c0e30c0b0cf8bf38c145cbf06422d40d076985195e1dd6trivy_0.69.4_Linux-PPC64LE.rpm
52518d441fd6dd25fa5126683a330592d3be80d5ce3fb9e0b1becb806ff4f857trivy_0.69.4_Linux-PPC64LE.tar.gz
62585efcdc7767f3fe0b9ae2897fe03bf331934492fd7a5da46f14fd7bf705c8trivy_0.69.4_Linux-s390x.deb
107be2081bdc3ddad2889ae037ab2ad6bbd214fb9a43eaa25390d00411d1c7ddtrivy_0.69.4_Linux-s390x.rpm
16c855c398a8b185a907790054b70164358844a893bf9965651b88d6967c7c0atrivy_0.69.4_Linux-s390x.tar.gz
90d61cf37355b89fae9ff84867100e1721c1876007ef1771e465ce5a721141adtrivy_0.69.4_macOS-64bit.tar.gz
1dc871b02cd7a1fd80babb1b8762a2fd9cc2b735d4d3759d012626de3ccc7a5btrivy_0.69.4_macOS-ARM64.tar.gz
0376b98064636c30f5fbe60fb3b1225516e23e88dd7e909937f81d9265292e7dtrivy_0.69.4_windows_64bit.zip
822dd269ec10459572dfaaefe163dae693c344249a0161953f0d5cdd110bd2a0trivy_0.69.4_linux_amd64
e64e152afe2c722d750f10259626f357cdea40420c5eedae37969fbf13abbecftrivy_0.69.4_linux_arm64
d5edd791021b966fb6af0ace09319ace7b97d6642363ef27b3d5056ca654a94ctrivy_0.69.4_s390x
ecce7ae5ffc9f57bb70efd3ea136a2923f701334a8cd47d4fbf01a97fd22859ctrivy_0.69.4_ppc64le
Container images (v0.69.4)
DigestTag
sha256:27f446230c60bbf0b70e008db798bd4f33b7826f9f76f756606f5417100beef30.69.4
sha256:12c702212dee1cbec9471e9261501a3335963321fe76e60e5a715b5acd3c40a20.69.4-linux/amd64
sha256:2d7cee41048988eec27615412e7c6e2e21046f2b5faa888c24e11ca6764058ed0.69.4-linux/arm64
sha256:ae3494bd6ae860d7727116681bd09fc7b20dc994ec7a8105738f0a623ea934270.69.4-linux/ppc64le
sha256:43f46547efd488e56dcf862ed4d7cc342730a803f8d5bec5cac443028fefabef0.69.4- linux/s390x
sha256:cc464a3961e1dbe145c75343b55c2f446e08b821782ec993728c4222b0d855890.69.4-signature
sha256:5aaa1d7cfa9ca4649d6ffad165435c519dc836fa6e21b729a2174ad10b057d2b0.69.5
sha256:95ff680103570179feb0c6667a9b9b2d98c53fa5a9a451265036810390bbe70a0.69.5-linux/arm64
sha256:4f7a06bb51714713ab308d2f8125f3b09ee1c3ffbba1a5ffd0cc80da95fbb6cc0.69.5-linux/ppc64le
sha256:edef8e5816eced552a909b878ff262c0c47776d3297bcc23796ad4cce1e854140.69.5-linux/s390x
sha256:425cd3e1a2846ac73944e891250377d2b03653e6f028833e30fc00c1abbc6d330.69.6
sha256:dd8beb3b40df080b3fd7f9a0f5a1b02f3692f65c68980f46da8328ce8bb788ef0.69.6-linux/amd64
sha256:4b22cedea58780ff76735c3e08b9ee8cb5d06c908ffa868152f11d45349eb6960.69.6-linux/arm64
sha256:9efd59534d2b6b81b8b7a0eeb3ad0e74015f358650e24b9dab00c900d31185930.69.6-linux/ppc64le
sha256:5e5fb53cf4ce5555171ff5206302ba2f4f66f5381bbf673c354c87a925473f070.69.6-linux/s390x
Network

C2/sinks:

  • scan.aquasecurtiy.org
  • 45.148.10.212
GitHub Repositories

Public repo on victim's GitHub account with tpcp-docs- prefix.
Stolen data uploaded as a release asset with tag data-<timestamp>.

Severity

  • CVSS Score: 9.4 / 10 (Critical)
  • 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

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Release Notes

aquasecurity/trivy-action (aquasecurity/trivy-action)

v0.35.0: Release: v0.35.0

Compare Source

This release is a duplicate of 0.35.0 which was not compromised.

As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.

We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.

If you are currently using 0.35.0, your workflows are safe — no action is required.

v0.35.0: Release: v0.35.0

Compare Source

This release is a duplicate of 0.35.0 which was not compromised.

As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.

We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.

If you are currently using 0.35.0, your workflows are safe — no action is required.

v0.34.0: Release: v0.34.0

Compare Source

Full Changelog: aquasecurity/trivy-action@v0.33.1...v0.34.0

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Footnotes

  1. Time when v0.69.4 release artifacts became publicly available. The malicious tag was pushed at ~17:43 UTC, triggering the release pipeline. ↩

  2. Earliest suspicious activity observed in our audit log. ↩↩2

@renovaterenovateBot added package:github-actions Pull requests that update action deps type:dependencies Pull requests that update a dependency file update:minor Minor Updates of dependency labels Mar 24, 2026
@snyk-io

snyk-ioBot commented Mar 24, 2026•
edited
Loading

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

StatusScan Engine Critical High Medium LowTotal (0)
✅Open Source Security0000 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@renovaterenovateBot changed the title chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMar 27, 2026
@renovaterenovateBot closed this Mar 27, 2026
@renovate
renovateBot deleted the renovate/github-tags-aquasecurity-trivy-action-vulnerability branch March 27, 2026 01:57
@renovaterenovateBot changed the title chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Mar 28, 2026
@renovaterenovateBot reopened this Mar 28, 2026
@renovate
renovateBotforce-pushed the renovate/github-tags-aquasecurity-trivy-action-vulnerability branch 2 times, most recently from 24158b3 to 8c3ea0aCompareMarch 28, 2026 01:05
@renovaterenovateBot changed the title chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedApr 4, 2026
@renovaterenovateBot closed this Apr 4, 2026
@renovaterenovateBot changed the title chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Apr 4, 2026
@renovaterenovateBot reopened this Apr 4, 2026
@renovate
renovateBotforce-pushed the renovate/github-tags-aquasecurity-trivy-action-vulnerability branch 2 times, most recently from 8c3ea0a to 58cfc9aCompareApril 4, 2026 20:54
@renovaterenovateBot added the status:ready-to-merge PR is ready to merge, skips approving label Apr 18, 2026
@renovaterenovateBot changed the title chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMay 1, 2026
@renovaterenovateBot closed this May 1, 2026
@renovaterenovateBot changed the title chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]May 2, 2026
@renovaterenovateBot reopened this May 2, 2026
@renovate
renovateBotforce-pushed the renovate/github-tags-aquasecurity-trivy-action-vulnerability branch 2 times, most recently from 58cfc9a to bc5d01cCompareMay 2, 2026 01:42
@renovaterenovateBot changed the title chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 10, 2026
@renovaterenovateBot closed this Jul 10, 2026
@renovaterenovateBot changed the title chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 10, 2026
@renovaterenovateBot reopened this Jul 10, 2026
@renovate
renovateBotforce-pushed the renovate/github-tags-aquasecurity-trivy-action-vulnerability branch 2 times, most recently from bc5d01c to 1b9d045CompareJuly 10, 2026 19:13
@renovaterenovateBot changed the title chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 16, 2026
@renovaterenovateBot closed this Jul 16, 2026
@renovaterenovateBot changed the title chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 16, 2026
@renovaterenovateBot reopened this Jul 16, 2026
@renovate
renovateBotforce-pushed the renovate/github-tags-aquasecurity-trivy-action-vulnerability branch 2 times, most recently from 1b9d045 to 06294b3CompareJuly 16, 2026 15:06
@renovaterenovateBot changed the title chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedAug 24, 2026
@renovaterenovateBot closed this Aug 24, 2026
@renovaterenovateBot changed the title chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Aug 25, 2026
@renovaterenovateBot reopened this Aug 25, 2026
@renovate
renovateBotforce-pushed the renovate/github-tags-aquasecurity-trivy-action-vulnerability branch from 06294b3 to 004fe91CompareAugust 25, 2026 20:12
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

package:github-actionsPull requests that update action depsstatus:ready-to-mergePR is ready to merge, skips approvingtype:dependenciesPull requests that update a dependency fileupdate:minorMinor Updates of dependency

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - #145
Open
renovate[bot] wants to merge 1 commit into
devfrom 
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Open
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]#145
renovate[bot] wants to merge 1 commit into
devfrom 
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Conversation
@renovate
@renovaterenovateBot
commented
Mar 24, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
This PR contains the following updates:
PackageTypeUpdateChange
aquasecurity/trivy-actionactionminor0.33.1 → 0.35.0
Trivy Action has a script injection via sourced env file in composite action
CVE-2026-26189 / GHSA-9p44-j4g5-cfx5
More information
Details
Command Injection in aquasecurity/trivy-action via Unsanitized Environment Variable Export
A command injection vulnerability exists in aquasecurity/trivy-action due to improper handling of action inputs when exporting environment variables. The action writes export VAR=<input> lines to trivy_envs.txt based on user-supplied inputs and subsequently sources this file in entrypoint.sh.
Because input values are written without appropriate shell escaping, attacker-controlled input containing shell metacharacters (e.g., $(...), backticks, or other command substitution syntax) may be evaluated during the sourcing process. This can result in arbitrary command execution within the GitHub Actions runner context.
Severity:
Moderate
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
CWE-78: Improper Neutralization of Special Elements used in an OS Command (‘OS Command Injection’)
Impact:
Successful exploitation may lead to arbitrary command execution in the CI runner environment.
Affected Versions:
  • Versions >= 0.31.0 and <= 0.33.1
  • Introduced in commit 7aca5ac
Affected Conditions:
The vulnerability is exploitable when a consuming workflow passes attacker-controlled data into any action input that is written to trivy_envs.txt. Access to user input is required by the malicious actor.
A representative exploitation pattern involves incorporating untrusted pull request metadata into an action parameter. For example:
- uses: aquasecurity/trivy-action@0.33.1with:
output: "trivy-$.sarif"
If the pull request title contains shell syntax, it may be executed when the generated environment file is sourced.
Not Affected:
  • Workflows that do not pass attacker-controlled data into trivy-action inputs
  • Workflows that upgrade to a patched version that properly escapes shell values or eliminates the source ./trivy_envs.txt pattern
  • Workflows where user input is not accessible.
Call Sites:
  • action.yaml:188 — set_env_var_if_provided writes unescaped export lines
  • entrypoint.sh:9 — sources ./trivy_envs.txt
Severity
  • CVSS Score: 5.9 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Trivy ecosystem supply chain was briefly compromised
CVE-2026-33634 / GHSA-69fq-xp46-6x23
More information
Details
Summary
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.

On March 22, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.5 and v0.69.6 DockerHub images.
Exposure Window
ComponentStart (UTC)End (UTC)Duration
trivy v0.69.42026-03-19 18:22 12026-03-19 ~21:42~3 hours
trivy-action2026-03-19 ~17:43 22026-03-20 ~05:40~12 hours
setup-trivy2026-03-19 ~17:43 22026-03-19 ~21:44~4 hours
dockerhub trivy images v0.69.5 and v0.69.62026-03-22 15:432026-03-23 ~01:40~10 hours
Affected Components
Note that all malicious components, artifacts, commits, etc have been removed from all sources and destinations (yet they may linger in intermediary caches). Use this information to understand if you have been exposed to the malicious artifacts during the exposure window.
trivy binary and image
You are affected if you used:
  1. trivy binaries version v0.69.4 (or latest during the exposure window) distributed via GitHub, Deb, RPM.
  2. trivy container images v0.69.4 (or latest during the exposure window) distributed via GHCR, ECR public, Docker Hub.
  3. trivy container images v0.69.5 and v0.69.6 (or latest during the exposure window) distributed via Docker Hub.
You are not affected if you used:
  1. trivy (binary or image) version v0.69.3 or earlier.

    1. v0.69.3 is protected by GitHub's immutable releases feature (enabled March 3, before v0.69.3 was published).
    2. v0.69.2 predates immutable releases enablement but integrity can be verified via sigstore signatures (see "How to Verify" section below).
  2. trivy images referenced by digest.
  3. trivy binaries built from source.

    1. The malicious code was not committed to Trivy's main branch. It was fetched and built on the ephemeral runner, and also committed to a v0.70.0 branch but no release or git tag was ever pushed.
  4. homebrew from official formula (brew install trivy)

    1. The official homebrew formula is building trivy directly from source.
    2. There's an additional custom trivy tap which was compromised as part of the v0.69.4 release, but that tap requires special installation and is not even mentioned in the trivy documentation.
aquasecurity/trivy-action GitHub Action
You are affected if you used:
  1. Any tags prior except 0.35.0 (0.0.1 – 0.34.2) to reference the action.
  2. the action's version: latest parameter explicitly (not the default) during the trivy binary exposure window.
  3. SHA pinning to a commit prior to 2025-04-09.

    1. trivy-action started pinning setup-go with pull request trivy-action#456. If you pinned trivy-action to a commit prior to that PR (merged 2025-04-09), then you would get a safe trivy-action but it would get a malicious setup-trivy, if invoked during the setup-trivy exposure window.
You are not affected if you used:
  1. 0.35.0 tag

    1. 0.35.0 is protected by GitHub's immutable releases feature (enabled March 4, before 0.35.0 was published) and was not affected by the tag hijacking attack.
  2. SHA pinning to a safe commit commit after 2025-04-09.
aquasecurity/setup-trivy GitHub Action
You are affected if you used:
  1. Any version without pinning.
You are not affected if you used:
  1. SHA pinning to a safe commit.
Attack Details
Root Cause
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.
Trivy v0.69.4 binary and container images
The attacker created a malicious release by:
  1. Pushing a commit (1885610c) that swapped the actions/checkout reference to an imposter commit (70379aad) containing a composite action that downloaded malicious Go source files from a typosquatted domain
  2. Adding --skip=validate to goreleaser to bypass binary validation
  3. Tagging this commit as v0.69.4, triggering the release pipeline
The compromised release was distributed across Trivy's regular distribution channels channels: GHCR, ECR Public, Docker Hub (both 0.69.4 and latest tags), deb/rpm packages, and get.trivy.dev.
The attacker attempted to release a v0.70.0 malicious release but that was stopped prematurely.
trivy-action tag hijacking
The attacker force-pushed 76 of 77 version tags to malicious commits that injected an infostealer into entrypoint.sh. The malicious code executes before the legitimate Trivy scan and does the following:
  1. Dumps Runner.Worker process memory via /proc/<pid>/mem to extract secrets. Sweeps 50+ filesystem paths for SSH keys, AWS/GCP/Azure credentials, Kubernetes tokens, Docker configs, .env files, database credentials, and cryptocurrency wallets.
  2. Encrypts collected data using AES-256-CBC with RSA-4096 hybrid encryption.
  3. Transmits to attacker-controlled infrastructure. If exfiltration fails and INPUT_GITHUB_PAT is set, creates a public tpcp-docs repository on the victim's GitHub account and uploads stolen data as a release asset.
setup-trivy release replacement
All 7 existing tags (v0.2.0 – v0.2.6) were force-pushed to malicious commits. The malicious action.yaml contained the same infostealer as trivy-action, injected as a "Setup environment" step that executes before the legitimate Trivy installation.

We have removed all malicious releases within ~4 hours and re-created v0.2.6 with safe content. Tags v0.2.0 – v0.2.5 were not restored.
Trivy v0.69.5 and v0.69.6 docker image published.
The attacker created aquasec/trivy:0.69.5 and aquasec/trivy:0.69.6 with the same C2 domain as the v0.69.4 payload, and pushed them directly to Docker Hub using separately-compromised Docker Hub credentials (not via GitHub). No corresponding GitHub tags or releases existed.

We have removed all tags related to 0.69.5 and 0.69.6 and restored the latest tag to the safe 0.69.3 tag.
Recommended Actions
Update to Known-Safe Versions
ComponentSafe Version
Trivy binaryv0.69.2, v0.69.3
trivy-actionv0.35.0
setup-trivyv0.2.6
Regarding trivy-action: The original tags (0.0.1 – 0.34.2) were deleted during remediation. Because the attacker's force-push caused these tags to be treated as immutable releases by GitHub, they cannot be re-created with the same names. New tags have been published with a v prefix (v0.0.1 – v0.34.2) pointing to the original legitimate commits. Three tags: v0.0.10, v0.34.1, and v0.34.2 have not yet been restored. If you need to reference a version older than 0.35.0, use the v-prefixed tag (e.g., aquasecurity/trivy-action@v0.34.0 instead of @0.34.0).
Rotate All Potentially Exposed Secrets
Based on information shared above, if there is any possibility that a compromised version ran in your environment, all secrets accessible to affected pipelines must be treated as exposed and rotated immediately.
Audit Trivy Versions
Check whether your organization pulled or executed Trivy v0.69.4 from any source. Remove any affected artifacts immediately.
Audit GitHub Action References
Review all workflows using aquasecurity/trivy-action or aquasecurity/setup-trivy. Check workflow run logs from March 19–20, 2026 for signs of compromise.
Search for Exfiltration Artifacts
Look for repositories named tpcp-docs in your 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 SHA Hashes
Pin GitHub Actions to full, immutable commit SHA hashes, don't use mutable version tags. As described here: https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions
How to Verify Existing Installations
Binary verification
##### Download binary and sigstore bundle
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz"
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json"##### Verify signature
$ cosign verify-blob \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--bundle trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json \
trivy_0.69.2_Linux-64bit.tar.gz
Verified OK
##### Check signing timestamp
$ date -u -d @$(jq -r '.verificationMaterial.tlogEntries[].integratedTime' trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json)
Sat Mar 1 19:11:02 UTC 2026
##### ✅ Signed on Mar 1, before the attack on Mar 19
Container image verification
##### Verify signature and get image digest
$ cosign verify \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--new-bundle-format \
ghcr.io/aquasecurity/trivy:0.69.2
Verification for ghcr.io/aquasecurity/trivy:0.69.2 --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The code-signing certificate was verified using trusted certificate authority certificates
##### Get digest and check all signing timestamps via Rekor
$ DIGEST=$(cosign verify \ --certificate-identity-regexp 'https://github\.com/aquasecurity/' \ --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \ --new-bundle-format -o json ghcr.io/aquasecurity/trivy:0.69.2 2>/dev/null | \ jq -r '.[0].critical.image."docker-manifest-digest"')
$ rekor-cli search --sha "$DIGEST"| grep -v 'Found'|whileread uuid;do
rekor-cli get --uuid "$uuid"| grep IntegratedTime
done
IntegratedTime: 2026-03-01T19:13:52Z
IntegratedTime: 2026-03-01T19:13:47Z
IntegratedTime: 2026-03-01T19:13:57Z
IntegratedTime: 2026-03-01T19:13:54Z
IntegratedTime: 2026-03-01T19:13:46Z
IntegratedTime: 2026-03-01T19:13:37Z
##### ✅ All signed on Mar 1, before the attack on Mar 19
Indicators of Compromise
Executable binaries
SHA256Filename
c5b16c42dbd2a1494141cd651a406ec9094d5031a421c0aa624c4d139ae81239trivy_0.69.4_FreeBSD_64bit.tar.gz
cff74e3e9ac0cda2078d31800d8fcad832d7b52c9920b085054d1e96dacff8a3trivy_0.69.4_Linux-32bit.deb
55047c55a5ceab6d80b13884b4a4e8cd27a0bab7a218a952a00aae9e05f16f80trivy_0.69.4_Linux-32bit.rpm
ba04ba6a0c028cde17599c8ddaefdb854055c5a23c595e06630732002ea59a76trivy_0.69.4_Linux-32bit.tar.gz
0ca60dd18178d1c79d59cc06be12c540c121a4aea467484244667131aa13c311trivy_0.69.4_Linux-64bit.deb
a5696321a6c93071f46c8bb8cbd0a8d2bce6d1860cc3c109247a4e8b64ebd317trivy_0.69.4_Linux-64bit.rpm
385d498d18a3a7c67878ca7322716f9da25683eb1a4bf9e9592da0d5f2ab09f6trivy_0.69.4_Linux-64bit.tar.gz
8f0c7b92b251c61cbca2add06c676dd21fde8fbb2d0cd6616383fae29b21756atrivy_0.69.4_Linux-ARM.deb
c5df9d1bc6275711b2884a9ed4aacfe4e10dbe3c8f6c79df59126fd0e6dcd83ftrivy_0.69.4_Linux-ARM.rpm
f7a9bbfec8add36c548add4d875848b8b57c21fabe236d115f1c49113d12b332trivy_0.69.4_Linux-ARM.tar.gz
9a833d68a49ec6d44bc50fb9ff3b184bafb0edc913e1293daebe51d334676a70trivy_0.69.4_Linux-ARM64.deb
451ce0c4deb620894d07a2f4a37c8ea3b7a4f9b6d111651b4ac3bcc737b0fac0trivy_0.69.4_Linux-ARM64.rpm
e401ae1e6d2442fa9a0c79dc0f3b0457ecfebf74a9c0a920159c49437f663aeftrivy_0.69.4_Linux-ARM64.tar.gz
284622577cf6a7c58704de60194205f765fcef432934c200b462ef0290aa5f57trivy_0.69.4_Linux-PPC64LE.deb
5fac89e66d70cadec5c0e30c0b0cf8bf38c145cbf06422d40d076985195e1dd6trivy_0.69.4_Linux-PPC64LE.rpm
52518d441fd6dd25fa5126683a330592d3be80d5ce3fb9e0b1becb806ff4f857trivy_0.69.4_Linux-PPC64LE.tar.gz
62585efcdc7767f3fe0b9ae2897fe03bf331934492fd7a5da46f14fd7bf705c8trivy_0.69.4_Linux-s390x.deb
107be2081bdc3ddad2889ae037ab2ad6bbd214fb9a43eaa25390d00411d1c7ddtrivy_0.69.4_Linux-s390x.rpm
16c855c398a8b185a907790054b70164358844a893bf9965651b88d6967c7c0atrivy_0.69.4_Linux-s390x.tar.gz
90d61cf37355b89fae9ff84867100e1721c1876007ef1771e465ce5a721141adtrivy_0.69.4_macOS-64bit.tar.gz
1dc871b02cd7a1fd80babb1b8762a2fd9cc2b735d4d3759d012626de3ccc7a5btrivy_0.69.4_macOS-ARM64.tar.gz
0376b98064636c30f5fbe60fb3b1225516e23e88dd7e909937f81d9265292e7dtrivy_0.69.4_windows_64bit.zip
822dd269ec10459572dfaaefe163dae693c344249a0161953f0d5cdd110bd2a0trivy_0.69.4_linux_amd64
e64e152afe2c722d750f10259626f357cdea40420c5eedae37969fbf13abbecftrivy_0.69.4_linux_arm64
d5edd791021b966fb6af0ace09319ace7b97d6642363ef27b3d5056ca654a94ctrivy_0.69.4_s390x
ecce7ae5ffc9f57bb70efd3ea136a2923f701334a8cd47d4fbf01a97fd22859ctrivy_0.69.4_ppc64le
Container images (v0.69.4)
DigestTag
sha256:27f446230c60bbf0b70e008db798bd4f33b7826f9f76f756606f5417100beef30.69.4
sha256:12c702212dee1cbec9471e9261501a3335963321fe76e60e5a715b5acd3c40a20.69.4-linux/amd64
sha256:2d7cee41048988eec27615412e7c6e2e21046f2b5faa888c24e11ca6764058ed0.69.4-linux/arm64
sha256:ae3494bd6ae860d7727116681bd09fc7b20dc994ec7a8105738f0a623ea934270.69.4-linux/ppc64le
sha256:43f46547efd488e56dcf862ed4d7cc342730a803f8d5bec5cac443028fefabef0.69.4- linux/s390x
sha256:cc464a3961e1dbe145c75343b55c2f446e08b821782ec993728c4222b0d855890.69.4-signature
sha256:5aaa1d7cfa9ca4649d6ffad165435c519dc836fa6e21b729a2174ad10b057d2b0.69.5
sha256:95ff680103570179feb0c6667a9b9b2d98c53fa5a9a451265036810390bbe70a0.69.5-linux/arm64
sha256:4f7a06bb51714713ab308d2f8125f3b09ee1c3ffbba1a5ffd0cc80da95fbb6cc0.69.5-linux/ppc64le
sha256:edef8e5816eced552a909b878ff262c0c47776d3297bcc23796ad4cce1e854140.69.5-linux/s390x
sha256:425cd3e1a2846ac73944e891250377d2b03653e6f028833e30fc00c1abbc6d330.69.6
sha256:dd8beb3b40df080b3fd7f9a0f5a1b02f3692f65c68980f46da8328ce8bb788ef0.69.6-linux/amd64
sha256:4b22cedea58780ff76735c3e08b9ee8cb5d06c908ffa868152f11d45349eb6960.69.6-linux/arm64
sha256:9efd59534d2b6b81b8b7a0eeb3ad0e74015f358650e24b9dab00c900d31185930.69.6-linux/ppc64le
sha256:5e5fb53cf4ce5555171ff5206302ba2f4f66f5381bbf673c354c87a925473f070.69.6-linux/s390x
Network
C2/sinks:
  • scan.aquasecurtiy.org
  • 45.148.10.212
GitHub Repositories
Public repo on victim's GitHub account with tpcp-docs- prefix.

Stolen data uploaded as a release asset with tag data-<timestamp>.
Severity
  • CVSS Score: 9.4 / 10 (Critical)
  • 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
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
aquasecurity/trivy-action (aquasecurity/trivy-action)
v0.35.0: Release: v0.35.0
Compare Source
This release is a duplicate of 0.35.0 which was not compromised.
As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.
We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.
If you are currently using 0.35.0, your workflows are safe — no action is required.
v0.35.0: Release: v0.35.0
Compare Source
This release is a duplicate of 0.35.0 which was not compromised.
As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.
We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.
If you are currently using 0.35.0, your workflows are safe — no action is required.
v0.34.0: Release: v0.34.0
Compare Source
Full Changelog: aquasecurity/trivy-action@v0.33.1...v0.34.0
Configuration
📅 Schedule: (UTC)
  • Branch creation

    • At any time (no schedule defined)
  • Automerge

    • At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
  •  If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Footnotes
  1. Time when v0.69.4 release artifacts became publicly available. The malicious tag was pushed at ~17:43 UTC, triggering the release pipeline. ↩
  2. Earliest suspicious activity observed in our audit log. ↩↩2
@renovaterenovateBot
added

package:github-actions
Pull requests that update action deps
type:dependencies
Pull requests that update a dependency file
update:minor
Minor Updates of dependency
labels
Mar 24, 2026
@snyk-io
snyk-ioBot
commented
Mar 24, 2026•

edited

Loading

Copy link


Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.
StatusScan Engine Critical High Medium LowTotal (0)
✅Open Source Security0000 0 issues
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMar 27, 2026
@renovaterenovateBot
closed this
Mar 27, 2026
@renovate
renovateBot
deleted the

renovate/github-tags-aquasecurity-trivy-action-vulnerability

branch
March 27, 2026 01:57
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Mar 28, 2026
@renovaterenovateBot
reopened this
Mar 28, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
24158b3 to
8c3ea0aCompareMarch 28, 2026 01:05
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedApr 4, 2026
@renovaterenovateBot
closed this
Apr 4, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Apr 4, 2026
@renovaterenovateBot
reopened this
Apr 4, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
8c3ea0a to
58cfc9aCompareApril 4, 2026 20:54
@renovaterenovateBot
added
the 
status:ready-to-merge
PR is ready to merge, skips approving
label
Apr 18, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMay 1, 2026
@renovaterenovateBot
closed this
May 1, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]May 2, 2026
@renovaterenovateBot
reopened this
May 2, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
58cfc9a to
bc5d01cCompareMay 2, 2026 01:42
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 10, 2026
@renovaterenovateBot
closed this
Jul 10, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 10, 2026
@renovaterenovateBot
reopened this
Jul 10, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
bc5d01c to
1b9d045CompareJuly 10, 2026 19:13
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 16, 2026
@renovaterenovateBot
closed this
Jul 16, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 16, 2026
@renovaterenovateBot
reopened this
Jul 16, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
1b9d045 to
06294b3CompareJuly 16, 2026 15:06
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedAug 24, 2026
@renovaterenovateBot
closed this
Aug 24, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Aug 25, 2026
@renovaterenovateBot
reopened this
Aug 25, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
from
06294b3 to
004fe91CompareAugust 25, 2026 20:12
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

package:github-actionsPull requests that update action depsstatus:ready-to-mergePR is ready to merge, skips approvingtype:dependenciesPull requests that update a dependency fileupdate:minorMinor Updates of dependency

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - #145
Open
renovate[bot] wants to merge 1 commit into
devfrom 
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Open
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]#145
renovate[bot] wants to merge 1 commit into
devfrom 
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Conversation
@renovate
@renovaterenovateBot
commented
Mar 24, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
This PR contains the following updates:
PackageTypeUpdateChange
aquasecurity/trivy-actionactionminor0.33.1 → 0.35.0
Trivy Action has a script injection via sourced env file in composite action
CVE-2026-26189 / GHSA-9p44-j4g5-cfx5
More information
Details
Command Injection in aquasecurity/trivy-action via Unsanitized Environment Variable Export
A command injection vulnerability exists in aquasecurity/trivy-action due to improper handling of action inputs when exporting environment variables. The action writes export VAR=<input> lines to trivy_envs.txt based on user-supplied inputs and subsequently sources this file in entrypoint.sh.
Because input values are written without appropriate shell escaping, attacker-controlled input containing shell metacharacters (e.g., $(...), backticks, or other command substitution syntax) may be evaluated during the sourcing process. This can result in arbitrary command execution within the GitHub Actions runner context.
Severity:
Moderate
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
CWE-78: Improper Neutralization of Special Elements used in an OS Command (‘OS Command Injection’)
Impact:
Successful exploitation may lead to arbitrary command execution in the CI runner environment.
Affected Versions:
  • Versions >= 0.31.0 and <= 0.33.1
  • Introduced in commit 7aca5ac
Affected Conditions:
The vulnerability is exploitable when a consuming workflow passes attacker-controlled data into any action input that is written to trivy_envs.txt. Access to user input is required by the malicious actor.
A representative exploitation pattern involves incorporating untrusted pull request metadata into an action parameter. For example:
- uses: aquasecurity/trivy-action@0.33.1with:
output: "trivy-$.sarif"
If the pull request title contains shell syntax, it may be executed when the generated environment file is sourced.
Not Affected:
  • Workflows that do not pass attacker-controlled data into trivy-action inputs
  • Workflows that upgrade to a patched version that properly escapes shell values or eliminates the source ./trivy_envs.txt pattern
  • Workflows where user input is not accessible.
Call Sites:
  • action.yaml:188 — set_env_var_if_provided writes unescaped export lines
  • entrypoint.sh:9 — sources ./trivy_envs.txt
Severity
  • CVSS Score: 5.9 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Trivy ecosystem supply chain was briefly compromised
CVE-2026-33634 / GHSA-69fq-xp46-6x23
More information
Details
Summary
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.

On March 22, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.5 and v0.69.6 DockerHub images.
Exposure Window
ComponentStart (UTC)End (UTC)Duration
trivy v0.69.42026-03-19 18:22 12026-03-19 ~21:42~3 hours
trivy-action2026-03-19 ~17:43 22026-03-20 ~05:40~12 hours
setup-trivy2026-03-19 ~17:43 22026-03-19 ~21:44~4 hours
dockerhub trivy images v0.69.5 and v0.69.62026-03-22 15:432026-03-23 ~01:40~10 hours
Affected Components
Note that all malicious components, artifacts, commits, etc have been removed from all sources and destinations (yet they may linger in intermediary caches). Use this information to understand if you have been exposed to the malicious artifacts during the exposure window.
trivy binary and image
You are affected if you used:
  1. trivy binaries version v0.69.4 (or latest during the exposure window) distributed via GitHub, Deb, RPM.
  2. trivy container images v0.69.4 (or latest during the exposure window) distributed via GHCR, ECR public, Docker Hub.
  3. trivy container images v0.69.5 and v0.69.6 (or latest during the exposure window) distributed via Docker Hub.
You are not affected if you used:
  1. trivy (binary or image) version v0.69.3 or earlier.

    1. v0.69.3 is protected by GitHub's immutable releases feature (enabled March 3, before v0.69.3 was published).
    2. v0.69.2 predates immutable releases enablement but integrity can be verified via sigstore signatures (see "How to Verify" section below).
  2. trivy images referenced by digest.
  3. trivy binaries built from source.

    1. The malicious code was not committed to Trivy's main branch. It was fetched and built on the ephemeral runner, and also committed to a v0.70.0 branch but no release or git tag was ever pushed.
  4. homebrew from official formula (brew install trivy)

    1. The official homebrew formula is building trivy directly from source.
    2. There's an additional custom trivy tap which was compromised as part of the v0.69.4 release, but that tap requires special installation and is not even mentioned in the trivy documentation.
aquasecurity/trivy-action GitHub Action
You are affected if you used:
  1. Any tags prior except 0.35.0 (0.0.1 – 0.34.2) to reference the action.
  2. the action's version: latest parameter explicitly (not the default) during the trivy binary exposure window.
  3. SHA pinning to a commit prior to 2025-04-09.

    1. trivy-action started pinning setup-go with pull request trivy-action#456. If you pinned trivy-action to a commit prior to that PR (merged 2025-04-09), then you would get a safe trivy-action but it would get a malicious setup-trivy, if invoked during the setup-trivy exposure window.
You are not affected if you used:
  1. 0.35.0 tag

    1. 0.35.0 is protected by GitHub's immutable releases feature (enabled March 4, before 0.35.0 was published) and was not affected by the tag hijacking attack.
  2. SHA pinning to a safe commit commit after 2025-04-09.
aquasecurity/setup-trivy GitHub Action
You are affected if you used:
  1. Any version without pinning.
You are not affected if you used:
  1. SHA pinning to a safe commit.
Attack Details
Root Cause
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.
Trivy v0.69.4 binary and container images
The attacker created a malicious release by:
  1. Pushing a commit (1885610c) that swapped the actions/checkout reference to an imposter commit (70379aad) containing a composite action that downloaded malicious Go source files from a typosquatted domain
  2. Adding --skip=validate to goreleaser to bypass binary validation
  3. Tagging this commit as v0.69.4, triggering the release pipeline
The compromised release was distributed across Trivy's regular distribution channels channels: GHCR, ECR Public, Docker Hub (both 0.69.4 and latest tags), deb/rpm packages, and get.trivy.dev.
The attacker attempted to release a v0.70.0 malicious release but that was stopped prematurely.
trivy-action tag hijacking
The attacker force-pushed 76 of 77 version tags to malicious commits that injected an infostealer into entrypoint.sh. The malicious code executes before the legitimate Trivy scan and does the following:
  1. Dumps Runner.Worker process memory via /proc/<pid>/mem to extract secrets. Sweeps 50+ filesystem paths for SSH keys, AWS/GCP/Azure credentials, Kubernetes tokens, Docker configs, .env files, database credentials, and cryptocurrency wallets.
  2. Encrypts collected data using AES-256-CBC with RSA-4096 hybrid encryption.
  3. Transmits to attacker-controlled infrastructure. If exfiltration fails and INPUT_GITHUB_PAT is set, creates a public tpcp-docs repository on the victim's GitHub account and uploads stolen data as a release asset.
setup-trivy release replacement
All 7 existing tags (v0.2.0 – v0.2.6) were force-pushed to malicious commits. The malicious action.yaml contained the same infostealer as trivy-action, injected as a "Setup environment" step that executes before the legitimate Trivy installation.

We have removed all malicious releases within ~4 hours and re-created v0.2.6 with safe content. Tags v0.2.0 – v0.2.5 were not restored.
Trivy v0.69.5 and v0.69.6 docker image published.
The attacker created aquasec/trivy:0.69.5 and aquasec/trivy:0.69.6 with the same C2 domain as the v0.69.4 payload, and pushed them directly to Docker Hub using separately-compromised Docker Hub credentials (not via GitHub). No corresponding GitHub tags or releases existed.

We have removed all tags related to 0.69.5 and 0.69.6 and restored the latest tag to the safe 0.69.3 tag.
Recommended Actions
Update to Known-Safe Versions
ComponentSafe Version
Trivy binaryv0.69.2, v0.69.3
trivy-actionv0.35.0
setup-trivyv0.2.6
Regarding trivy-action: The original tags (0.0.1 – 0.34.2) were deleted during remediation. Because the attacker's force-push caused these tags to be treated as immutable releases by GitHub, they cannot be re-created with the same names. New tags have been published with a v prefix (v0.0.1 – v0.34.2) pointing to the original legitimate commits. Three tags: v0.0.10, v0.34.1, and v0.34.2 have not yet been restored. If you need to reference a version older than 0.35.0, use the v-prefixed tag (e.g., aquasecurity/trivy-action@v0.34.0 instead of @0.34.0).
Rotate All Potentially Exposed Secrets
Based on information shared above, if there is any possibility that a compromised version ran in your environment, all secrets accessible to affected pipelines must be treated as exposed and rotated immediately.
Audit Trivy Versions
Check whether your organization pulled or executed Trivy v0.69.4 from any source. Remove any affected artifacts immediately.
Audit GitHub Action References
Review all workflows using aquasecurity/trivy-action or aquasecurity/setup-trivy. Check workflow run logs from March 19–20, 2026 for signs of compromise.
Search for Exfiltration Artifacts
Look for repositories named tpcp-docs in your 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 SHA Hashes
Pin GitHub Actions to full, immutable commit SHA hashes, don't use mutable version tags. As described here: https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions
How to Verify Existing Installations
Binary verification
##### Download binary and sigstore bundle
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz"
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json"##### Verify signature
$ cosign verify-blob \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--bundle trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json \
trivy_0.69.2_Linux-64bit.tar.gz
Verified OK
##### Check signing timestamp
$ date -u -d @$(jq -r '.verificationMaterial.tlogEntries[].integratedTime' trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json)
Sat Mar 1 19:11:02 UTC 2026
##### ✅ Signed on Mar 1, before the attack on Mar 19
Container image verification
##### Verify signature and get image digest
$ cosign verify \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--new-bundle-format \
ghcr.io/aquasecurity/trivy:0.69.2
Verification for ghcr.io/aquasecurity/trivy:0.69.2 --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The code-signing certificate was verified using trusted certificate authority certificates
##### Get digest and check all signing timestamps via Rekor
$ DIGEST=$(cosign verify \ --certificate-identity-regexp 'https://github\.com/aquasecurity/' \ --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \ --new-bundle-format -o json ghcr.io/aquasecurity/trivy:0.69.2 2>/dev/null | \ jq -r '.[0].critical.image."docker-manifest-digest"')
$ rekor-cli search --sha "$DIGEST"| grep -v 'Found'|whileread uuid;do
rekor-cli get --uuid "$uuid"| grep IntegratedTime
done
IntegratedTime: 2026-03-01T19:13:52Z
IntegratedTime: 2026-03-01T19:13:47Z
IntegratedTime: 2026-03-01T19:13:57Z
IntegratedTime: 2026-03-01T19:13:54Z
IntegratedTime: 2026-03-01T19:13:46Z
IntegratedTime: 2026-03-01T19:13:37Z
##### ✅ All signed on Mar 1, before the attack on Mar 19
Indicators of Compromise
Executable binaries
SHA256Filename
c5b16c42dbd2a1494141cd651a406ec9094d5031a421c0aa624c4d139ae81239trivy_0.69.4_FreeBSD_64bit.tar.gz
cff74e3e9ac0cda2078d31800d8fcad832d7b52c9920b085054d1e96dacff8a3trivy_0.69.4_Linux-32bit.deb
55047c55a5ceab6d80b13884b4a4e8cd27a0bab7a218a952a00aae9e05f16f80trivy_0.69.4_Linux-32bit.rpm
ba04ba6a0c028cde17599c8ddaefdb854055c5a23c595e06630732002ea59a76trivy_0.69.4_Linux-32bit.tar.gz
0ca60dd18178d1c79d59cc06be12c540c121a4aea467484244667131aa13c311trivy_0.69.4_Linux-64bit.deb
a5696321a6c93071f46c8bb8cbd0a8d2bce6d1860cc3c109247a4e8b64ebd317trivy_0.69.4_Linux-64bit.rpm
385d498d18a3a7c67878ca7322716f9da25683eb1a4bf9e9592da0d5f2ab09f6trivy_0.69.4_Linux-64bit.tar.gz
8f0c7b92b251c61cbca2add06c676dd21fde8fbb2d0cd6616383fae29b21756atrivy_0.69.4_Linux-ARM.deb
c5df9d1bc6275711b2884a9ed4aacfe4e10dbe3c8f6c79df59126fd0e6dcd83ftrivy_0.69.4_Linux-ARM.rpm
f7a9bbfec8add36c548add4d875848b8b57c21fabe236d115f1c49113d12b332trivy_0.69.4_Linux-ARM.tar.gz
9a833d68a49ec6d44bc50fb9ff3b184bafb0edc913e1293daebe51d334676a70trivy_0.69.4_Linux-ARM64.deb
451ce0c4deb620894d07a2f4a37c8ea3b7a4f9b6d111651b4ac3bcc737b0fac0trivy_0.69.4_Linux-ARM64.rpm
e401ae1e6d2442fa9a0c79dc0f3b0457ecfebf74a9c0a920159c49437f663aeftrivy_0.69.4_Linux-ARM64.tar.gz
284622577cf6a7c58704de60194205f765fcef432934c200b462ef0290aa5f57trivy_0.69.4_Linux-PPC64LE.deb
5fac89e66d70cadec5c0e30c0b0cf8bf38c145cbf06422d40d076985195e1dd6trivy_0.69.4_Linux-PPC64LE.rpm
52518d441fd6dd25fa5126683a330592d3be80d5ce3fb9e0b1becb806ff4f857trivy_0.69.4_Linux-PPC64LE.tar.gz
62585efcdc7767f3fe0b9ae2897fe03bf331934492fd7a5da46f14fd7bf705c8trivy_0.69.4_Linux-s390x.deb
107be2081bdc3ddad2889ae037ab2ad6bbd214fb9a43eaa25390d00411d1c7ddtrivy_0.69.4_Linux-s390x.rpm
16c855c398a8b185a907790054b70164358844a893bf9965651b88d6967c7c0atrivy_0.69.4_Linux-s390x.tar.gz
90d61cf37355b89fae9ff84867100e1721c1876007ef1771e465ce5a721141adtrivy_0.69.4_macOS-64bit.tar.gz
1dc871b02cd7a1fd80babb1b8762a2fd9cc2b735d4d3759d012626de3ccc7a5btrivy_0.69.4_macOS-ARM64.tar.gz
0376b98064636c30f5fbe60fb3b1225516e23e88dd7e909937f81d9265292e7dtrivy_0.69.4_windows_64bit.zip
822dd269ec10459572dfaaefe163dae693c344249a0161953f0d5cdd110bd2a0trivy_0.69.4_linux_amd64
e64e152afe2c722d750f10259626f357cdea40420c5eedae37969fbf13abbecftrivy_0.69.4_linux_arm64
d5edd791021b966fb6af0ace09319ace7b97d6642363ef27b3d5056ca654a94ctrivy_0.69.4_s390x
ecce7ae5ffc9f57bb70efd3ea136a2923f701334a8cd47d4fbf01a97fd22859ctrivy_0.69.4_ppc64le
Container images (v0.69.4)
DigestTag
sha256:27f446230c60bbf0b70e008db798bd4f33b7826f9f76f756606f5417100beef30.69.4
sha256:12c702212dee1cbec9471e9261501a3335963321fe76e60e5a715b5acd3c40a20.69.4-linux/amd64
sha256:2d7cee41048988eec27615412e7c6e2e21046f2b5faa888c24e11ca6764058ed0.69.4-linux/arm64
sha256:ae3494bd6ae860d7727116681bd09fc7b20dc994ec7a8105738f0a623ea934270.69.4-linux/ppc64le
sha256:43f46547efd488e56dcf862ed4d7cc342730a803f8d5bec5cac443028fefabef0.69.4- linux/s390x
sha256:cc464a3961e1dbe145c75343b55c2f446e08b821782ec993728c4222b0d855890.69.4-signature
sha256:5aaa1d7cfa9ca4649d6ffad165435c519dc836fa6e21b729a2174ad10b057d2b0.69.5
sha256:95ff680103570179feb0c6667a9b9b2d98c53fa5a9a451265036810390bbe70a0.69.5-linux/arm64
sha256:4f7a06bb51714713ab308d2f8125f3b09ee1c3ffbba1a5ffd0cc80da95fbb6cc0.69.5-linux/ppc64le
sha256:edef8e5816eced552a909b878ff262c0c47776d3297bcc23796ad4cce1e854140.69.5-linux/s390x
sha256:425cd3e1a2846ac73944e891250377d2b03653e6f028833e30fc00c1abbc6d330.69.6
sha256:dd8beb3b40df080b3fd7f9a0f5a1b02f3692f65c68980f46da8328ce8bb788ef0.69.6-linux/amd64
sha256:4b22cedea58780ff76735c3e08b9ee8cb5d06c908ffa868152f11d45349eb6960.69.6-linux/arm64
sha256:9efd59534d2b6b81b8b7a0eeb3ad0e74015f358650e24b9dab00c900d31185930.69.6-linux/ppc64le
sha256:5e5fb53cf4ce5555171ff5206302ba2f4f66f5381bbf673c354c87a925473f070.69.6-linux/s390x
Network
C2/sinks:
  • scan.aquasecurtiy.org
  • 45.148.10.212
GitHub Repositories
Public repo on victim's GitHub account with tpcp-docs- prefix.

Stolen data uploaded as a release asset with tag data-<timestamp>.
Severity
  • CVSS Score: 9.4 / 10 (Critical)
  • 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
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
aquasecurity/trivy-action (aquasecurity/trivy-action)
v0.35.0: Release: v0.35.0
Compare Source
This release is a duplicate of 0.35.0 which was not compromised.
As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.
We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.
If you are currently using 0.35.0, your workflows are safe — no action is required.
v0.35.0: Release: v0.35.0
Compare Source
This release is a duplicate of 0.35.0 which was not compromised.
As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.
We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.
If you are currently using 0.35.0, your workflows are safe — no action is required.
v0.34.0: Release: v0.34.0
Compare Source
Full Changelog: aquasecurity/trivy-action@v0.33.1...v0.34.0
Configuration
📅 Schedule: (UTC)
  • Branch creation

    • At any time (no schedule defined)
  • Automerge

    • At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
  •  If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Footnotes
  1. Time when v0.69.4 release artifacts became publicly available. The malicious tag was pushed at ~17:43 UTC, triggering the release pipeline. ↩
  2. Earliest suspicious activity observed in our audit log. ↩↩2
@renovaterenovateBot
added

package:github-actions
Pull requests that update action deps
type:dependencies
Pull requests that update a dependency file
update:minor
Minor Updates of dependency
labels
Mar 24, 2026
@snyk-io
snyk-ioBot
commented
Mar 24, 2026•

edited

Loading

Copy link


Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.
StatusScan Engine Critical High Medium LowTotal (0)
✅Open Source Security0000 0 issues
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMar 27, 2026
@renovaterenovateBot
closed this
Mar 27, 2026
@renovate
renovateBot
deleted the

renovate/github-tags-aquasecurity-trivy-action-vulnerability

branch
March 27, 2026 01:57
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Mar 28, 2026
@renovaterenovateBot
reopened this
Mar 28, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
24158b3 to
8c3ea0aCompareMarch 28, 2026 01:05
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedApr 4, 2026
@renovaterenovateBot
closed this
Apr 4, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Apr 4, 2026
@renovaterenovateBot
reopened this
Apr 4, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
8c3ea0a to
58cfc9aCompareApril 4, 2026 20:54
@renovaterenovateBot
added
the 
status:ready-to-merge
PR is ready to merge, skips approving
label
Apr 18, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMay 1, 2026
@renovaterenovateBot
closed this
May 1, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]May 2, 2026
@renovaterenovateBot
reopened this
May 2, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
58cfc9a to
bc5d01cCompareMay 2, 2026 01:42
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 10, 2026
@renovaterenovateBot
closed this
Jul 10, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 10, 2026
@renovaterenovateBot
reopened this
Jul 10, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
bc5d01c to
1b9d045CompareJuly 10, 2026 19:13
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 16, 2026
@renovaterenovateBot
closed this
Jul 16, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 16, 2026
@renovaterenovateBot
reopened this
Jul 16, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
1b9d045 to
06294b3CompareJuly 16, 2026 15:06
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedAug 24, 2026
@renovaterenovateBot
closed this
Aug 24, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Aug 25, 2026
@renovaterenovateBot
reopened this
Aug 25, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
from
06294b3 to
004fe91CompareAugust 25, 2026 20:12
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

package:github-actionsPull requests that update action depsstatus:ready-to-mergePR is ready to merge, skips approvingtype:dependenciesPull requests that update a dependency fileupdate:minorMinor Updates of dependency

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - #145
Open
renovate[bot] wants to merge 1 commit into
devfrom 
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Open
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]#145
renovate[bot] wants to merge 1 commit into
devfrom 
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Conversation
@renovate
@renovaterenovateBot
commented
Mar 24, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
This PR contains the following updates:
PackageTypeUpdateChange
aquasecurity/trivy-actionactionminor0.33.1 → 0.35.0
Trivy Action has a script injection via sourced env file in composite action
CVE-2026-26189 / GHSA-9p44-j4g5-cfx5
More information
Details
Command Injection in aquasecurity/trivy-action via Unsanitized Environment Variable Export
A command injection vulnerability exists in aquasecurity/trivy-action due to improper handling of action inputs when exporting environment variables. The action writes export VAR=<input> lines to trivy_envs.txt based on user-supplied inputs and subsequently sources this file in entrypoint.sh.
Because input values are written without appropriate shell escaping, attacker-controlled input containing shell metacharacters (e.g., $(...), backticks, or other command substitution syntax) may be evaluated during the sourcing process. This can result in arbitrary command execution within the GitHub Actions runner context.
Severity:
Moderate
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
CWE-78: Improper Neutralization of Special Elements used in an OS Command (‘OS Command Injection’)
Impact:
Successful exploitation may lead to arbitrary command execution in the CI runner environment.
Affected Versions:
  • Versions >= 0.31.0 and <= 0.33.1
  • Introduced in commit 7aca5ac
Affected Conditions:
The vulnerability is exploitable when a consuming workflow passes attacker-controlled data into any action input that is written to trivy_envs.txt. Access to user input is required by the malicious actor.
A representative exploitation pattern involves incorporating untrusted pull request metadata into an action parameter. For example:
- uses: aquasecurity/trivy-action@0.33.1with:
output: "trivy-$.sarif"
If the pull request title contains shell syntax, it may be executed when the generated environment file is sourced.
Not Affected:
  • Workflows that do not pass attacker-controlled data into trivy-action inputs
  • Workflows that upgrade to a patched version that properly escapes shell values or eliminates the source ./trivy_envs.txt pattern
  • Workflows where user input is not accessible.
Call Sites:
  • action.yaml:188 — set_env_var_if_provided writes unescaped export lines
  • entrypoint.sh:9 — sources ./trivy_envs.txt
Severity
  • CVSS Score: 5.9 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Trivy ecosystem supply chain was briefly compromised
CVE-2026-33634 / GHSA-69fq-xp46-6x23
More information
Details
Summary
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.

On March 22, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.5 and v0.69.6 DockerHub images.
Exposure Window
ComponentStart (UTC)End (UTC)Duration
trivy v0.69.42026-03-19 18:22 12026-03-19 ~21:42~3 hours
trivy-action2026-03-19 ~17:43 22026-03-20 ~05:40~12 hours
setup-trivy2026-03-19 ~17:43 22026-03-19 ~21:44~4 hours
dockerhub trivy images v0.69.5 and v0.69.62026-03-22 15:432026-03-23 ~01:40~10 hours
Affected Components
Note that all malicious components, artifacts, commits, etc have been removed from all sources and destinations (yet they may linger in intermediary caches). Use this information to understand if you have been exposed to the malicious artifacts during the exposure window.
trivy binary and image
You are affected if you used:
  1. trivy binaries version v0.69.4 (or latest during the exposure window) distributed via GitHub, Deb, RPM.
  2. trivy container images v0.69.4 (or latest during the exposure window) distributed via GHCR, ECR public, Docker Hub.
  3. trivy container images v0.69.5 and v0.69.6 (or latest during the exposure window) distributed via Docker Hub.
You are not affected if you used:
  1. trivy (binary or image) version v0.69.3 or earlier.

    1. v0.69.3 is protected by GitHub's immutable releases feature (enabled March 3, before v0.69.3 was published).
    2. v0.69.2 predates immutable releases enablement but integrity can be verified via sigstore signatures (see "How to Verify" section below).
  2. trivy images referenced by digest.
  3. trivy binaries built from source.

    1. The malicious code was not committed to Trivy's main branch. It was fetched and built on the ephemeral runner, and also committed to a v0.70.0 branch but no release or git tag was ever pushed.
  4. homebrew from official formula (brew install trivy)

    1. The official homebrew formula is building trivy directly from source.
    2. There's an additional custom trivy tap which was compromised as part of the v0.69.4 release, but that tap requires special installation and is not even mentioned in the trivy documentation.
aquasecurity/trivy-action GitHub Action
You are affected if you used:
  1. Any tags prior except 0.35.0 (0.0.1 – 0.34.2) to reference the action.
  2. the action's version: latest parameter explicitly (not the default) during the trivy binary exposure window.
  3. SHA pinning to a commit prior to 2025-04-09.

    1. trivy-action started pinning setup-go with pull request trivy-action#456. If you pinned trivy-action to a commit prior to that PR (merged 2025-04-09), then you would get a safe trivy-action but it would get a malicious setup-trivy, if invoked during the setup-trivy exposure window.
You are not affected if you used:
  1. 0.35.0 tag

    1. 0.35.0 is protected by GitHub's immutable releases feature (enabled March 4, before 0.35.0 was published) and was not affected by the tag hijacking attack.
  2. SHA pinning to a safe commit commit after 2025-04-09.
aquasecurity/setup-trivy GitHub Action
You are affected if you used:
  1. Any version without pinning.
You are not affected if you used:
  1. SHA pinning to a safe commit.
Attack Details
Root Cause
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.
Trivy v0.69.4 binary and container images
The attacker created a malicious release by:
  1. Pushing a commit (1885610c) that swapped the actions/checkout reference to an imposter commit (70379aad) containing a composite action that downloaded malicious Go source files from a typosquatted domain
  2. Adding --skip=validate to goreleaser to bypass binary validation
  3. Tagging this commit as v0.69.4, triggering the release pipeline
The compromised release was distributed across Trivy's regular distribution channels channels: GHCR, ECR Public, Docker Hub (both 0.69.4 and latest tags), deb/rpm packages, and get.trivy.dev.
The attacker attempted to release a v0.70.0 malicious release but that was stopped prematurely.
trivy-action tag hijacking
The attacker force-pushed 76 of 77 version tags to malicious commits that injected an infostealer into entrypoint.sh. The malicious code executes before the legitimate Trivy scan and does the following:
  1. Dumps Runner.Worker process memory via /proc/<pid>/mem to extract secrets. Sweeps 50+ filesystem paths for SSH keys, AWS/GCP/Azure credentials, Kubernetes tokens, Docker configs, .env files, database credentials, and cryptocurrency wallets.
  2. Encrypts collected data using AES-256-CBC with RSA-4096 hybrid encryption.
  3. Transmits to attacker-controlled infrastructure. If exfiltration fails and INPUT_GITHUB_PAT is set, creates a public tpcp-docs repository on the victim's GitHub account and uploads stolen data as a release asset.
setup-trivy release replacement
All 7 existing tags (v0.2.0 – v0.2.6) were force-pushed to malicious commits. The malicious action.yaml contained the same infostealer as trivy-action, injected as a "Setup environment" step that executes before the legitimate Trivy installation.

We have removed all malicious releases within ~4 hours and re-created v0.2.6 with safe content. Tags v0.2.0 – v0.2.5 were not restored.
Trivy v0.69.5 and v0.69.6 docker image published.
The attacker created aquasec/trivy:0.69.5 and aquasec/trivy:0.69.6 with the same C2 domain as the v0.69.4 payload, and pushed them directly to Docker Hub using separately-compromised Docker Hub credentials (not via GitHub). No corresponding GitHub tags or releases existed.

We have removed all tags related to 0.69.5 and 0.69.6 and restored the latest tag to the safe 0.69.3 tag.
Recommended Actions
Update to Known-Safe Versions
ComponentSafe Version
Trivy binaryv0.69.2, v0.69.3
trivy-actionv0.35.0
setup-trivyv0.2.6
Regarding trivy-action: The original tags (0.0.1 – 0.34.2) were deleted during remediation. Because the attacker's force-push caused these tags to be treated as immutable releases by GitHub, they cannot be re-created with the same names. New tags have been published with a v prefix (v0.0.1 – v0.34.2) pointing to the original legitimate commits. Three tags: v0.0.10, v0.34.1, and v0.34.2 have not yet been restored. If you need to reference a version older than 0.35.0, use the v-prefixed tag (e.g., aquasecurity/trivy-action@v0.34.0 instead of @0.34.0).
Rotate All Potentially Exposed Secrets
Based on information shared above, if there is any possibility that a compromised version ran in your environment, all secrets accessible to affected pipelines must be treated as exposed and rotated immediately.
Audit Trivy Versions
Check whether your organization pulled or executed Trivy v0.69.4 from any source. Remove any affected artifacts immediately.
Audit GitHub Action References
Review all workflows using aquasecurity/trivy-action or aquasecurity/setup-trivy. Check workflow run logs from March 19–20, 2026 for signs of compromise.
Search for Exfiltration Artifacts
Look for repositories named tpcp-docs in your 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 SHA Hashes
Pin GitHub Actions to full, immutable commit SHA hashes, don't use mutable version tags. As described here: https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions
How to Verify Existing Installations
Binary verification
##### Download binary and sigstore bundle
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz"
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json"##### Verify signature
$ cosign verify-blob \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--bundle trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json \
trivy_0.69.2_Linux-64bit.tar.gz
Verified OK
##### Check signing timestamp
$ date -u -d @$(jq -r '.verificationMaterial.tlogEntries[].integratedTime' trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json)
Sat Mar 1 19:11:02 UTC 2026
##### ✅ Signed on Mar 1, before the attack on Mar 19
Container image verification
##### Verify signature and get image digest
$ cosign verify \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--new-bundle-format \
ghcr.io/aquasecurity/trivy:0.69.2
Verification for ghcr.io/aquasecurity/trivy:0.69.2 --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The code-signing certificate was verified using trusted certificate authority certificates
##### Get digest and check all signing timestamps via Rekor
$ DIGEST=$(cosign verify \ --certificate-identity-regexp 'https://github\.com/aquasecurity/' \ --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \ --new-bundle-format -o json ghcr.io/aquasecurity/trivy:0.69.2 2>/dev/null | \ jq -r '.[0].critical.image."docker-manifest-digest"')
$ rekor-cli search --sha "$DIGEST"| grep -v 'Found'|whileread uuid;do
rekor-cli get --uuid "$uuid"| grep IntegratedTime
done
IntegratedTime: 2026-03-01T19:13:52Z
IntegratedTime: 2026-03-01T19:13:47Z
IntegratedTime: 2026-03-01T19:13:57Z
IntegratedTime: 2026-03-01T19:13:54Z
IntegratedTime: 2026-03-01T19:13:46Z
IntegratedTime: 2026-03-01T19:13:37Z
##### ✅ All signed on Mar 1, before the attack on Mar 19
Indicators of Compromise
Executable binaries
SHA256Filename
c5b16c42dbd2a1494141cd651a406ec9094d5031a421c0aa624c4d139ae81239trivy_0.69.4_FreeBSD_64bit.tar.gz
cff74e3e9ac0cda2078d31800d8fcad832d7b52c9920b085054d1e96dacff8a3trivy_0.69.4_Linux-32bit.deb
55047c55a5ceab6d80b13884b4a4e8cd27a0bab7a218a952a00aae9e05f16f80trivy_0.69.4_Linux-32bit.rpm
ba04ba6a0c028cde17599c8ddaefdb854055c5a23c595e06630732002ea59a76trivy_0.69.4_Linux-32bit.tar.gz
0ca60dd18178d1c79d59cc06be12c540c121a4aea467484244667131aa13c311trivy_0.69.4_Linux-64bit.deb
a5696321a6c93071f46c8bb8cbd0a8d2bce6d1860cc3c109247a4e8b64ebd317trivy_0.69.4_Linux-64bit.rpm
385d498d18a3a7c67878ca7322716f9da25683eb1a4bf9e9592da0d5f2ab09f6trivy_0.69.4_Linux-64bit.tar.gz
8f0c7b92b251c61cbca2add06c676dd21fde8fbb2d0cd6616383fae29b21756atrivy_0.69.4_Linux-ARM.deb
c5df9d1bc6275711b2884a9ed4aacfe4e10dbe3c8f6c79df59126fd0e6dcd83ftrivy_0.69.4_Linux-ARM.rpm
f7a9bbfec8add36c548add4d875848b8b57c21fabe236d115f1c49113d12b332trivy_0.69.4_Linux-ARM.tar.gz
9a833d68a49ec6d44bc50fb9ff3b184bafb0edc913e1293daebe51d334676a70trivy_0.69.4_Linux-ARM64.deb
451ce0c4deb620894d07a2f4a37c8ea3b7a4f9b6d111651b4ac3bcc737b0fac0trivy_0.69.4_Linux-ARM64.rpm
e401ae1e6d2442fa9a0c79dc0f3b0457ecfebf74a9c0a920159c49437f663aeftrivy_0.69.4_Linux-ARM64.tar.gz
284622577cf6a7c58704de60194205f765fcef432934c200b462ef0290aa5f57trivy_0.69.4_Linux-PPC64LE.deb
5fac89e66d70cadec5c0e30c0b0cf8bf38c145cbf06422d40d076985195e1dd6trivy_0.69.4_Linux-PPC64LE.rpm
52518d441fd6dd25fa5126683a330592d3be80d5ce3fb9e0b1becb806ff4f857trivy_0.69.4_Linux-PPC64LE.tar.gz
62585efcdc7767f3fe0b9ae2897fe03bf331934492fd7a5da46f14fd7bf705c8trivy_0.69.4_Linux-s390x.deb
107be2081bdc3ddad2889ae037ab2ad6bbd214fb9a43eaa25390d00411d1c7ddtrivy_0.69.4_Linux-s390x.rpm
16c855c398a8b185a907790054b70164358844a893bf9965651b88d6967c7c0atrivy_0.69.4_Linux-s390x.tar.gz
90d61cf37355b89fae9ff84867100e1721c1876007ef1771e465ce5a721141adtrivy_0.69.4_macOS-64bit.tar.gz
1dc871b02cd7a1fd80babb1b8762a2fd9cc2b735d4d3759d012626de3ccc7a5btrivy_0.69.4_macOS-ARM64.tar.gz
0376b98064636c30f5fbe60fb3b1225516e23e88dd7e909937f81d9265292e7dtrivy_0.69.4_windows_64bit.zip
822dd269ec10459572dfaaefe163dae693c344249a0161953f0d5cdd110bd2a0trivy_0.69.4_linux_amd64
e64e152afe2c722d750f10259626f357cdea40420c5eedae37969fbf13abbecftrivy_0.69.4_linux_arm64
d5edd791021b966fb6af0ace09319ace7b97d6642363ef27b3d5056ca654a94ctrivy_0.69.4_s390x
ecce7ae5ffc9f57bb70efd3ea136a2923f701334a8cd47d4fbf01a97fd22859ctrivy_0.69.4_ppc64le
Container images (v0.69.4)
DigestTag
sha256:27f446230c60bbf0b70e008db798bd4f33b7826f9f76f756606f5417100beef30.69.4
sha256:12c702212dee1cbec9471e9261501a3335963321fe76e60e5a715b5acd3c40a20.69.4-linux/amd64
sha256:2d7cee41048988eec27615412e7c6e2e21046f2b5faa888c24e11ca6764058ed0.69.4-linux/arm64
sha256:ae3494bd6ae860d7727116681bd09fc7b20dc994ec7a8105738f0a623ea934270.69.4-linux/ppc64le
sha256:43f46547efd488e56dcf862ed4d7cc342730a803f8d5bec5cac443028fefabef0.69.4- linux/s390x
sha256:cc464a3961e1dbe145c75343b55c2f446e08b821782ec993728c4222b0d855890.69.4-signature
sha256:5aaa1d7cfa9ca4649d6ffad165435c519dc836fa6e21b729a2174ad10b057d2b0.69.5
sha256:95ff680103570179feb0c6667a9b9b2d98c53fa5a9a451265036810390bbe70a0.69.5-linux/arm64
sha256:4f7a06bb51714713ab308d2f8125f3b09ee1c3ffbba1a5ffd0cc80da95fbb6cc0.69.5-linux/ppc64le
sha256:edef8e5816eced552a909b878ff262c0c47776d3297bcc23796ad4cce1e854140.69.5-linux/s390x
sha256:425cd3e1a2846ac73944e891250377d2b03653e6f028833e30fc00c1abbc6d330.69.6
sha256:dd8beb3b40df080b3fd7f9a0f5a1b02f3692f65c68980f46da8328ce8bb788ef0.69.6-linux/amd64
sha256:4b22cedea58780ff76735c3e08b9ee8cb5d06c908ffa868152f11d45349eb6960.69.6-linux/arm64
sha256:9efd59534d2b6b81b8b7a0eeb3ad0e74015f358650e24b9dab00c900d31185930.69.6-linux/ppc64le
sha256:5e5fb53cf4ce5555171ff5206302ba2f4f66f5381bbf673c354c87a925473f070.69.6-linux/s390x
Network
C2/sinks:
  • scan.aquasecurtiy.org
  • 45.148.10.212
GitHub Repositories
Public repo on victim's GitHub account with tpcp-docs- prefix.

Stolen data uploaded as a release asset with tag data-<timestamp>.
Severity
  • CVSS Score: 9.4 / 10 (Critical)
  • 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
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
aquasecurity/trivy-action (aquasecurity/trivy-action)
v0.35.0: Release: v0.35.0
Compare Source
This release is a duplicate of 0.35.0 which was not compromised.
As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.
We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.
If you are currently using 0.35.0, your workflows are safe — no action is required.
v0.35.0: Release: v0.35.0
Compare Source
This release is a duplicate of 0.35.0 which was not compromised.
As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.
We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.
If you are currently using 0.35.0, your workflows are safe — no action is required.
v0.34.0: Release: v0.34.0
Compare Source
Full Changelog: aquasecurity/trivy-action@v0.33.1...v0.34.0
Configuration
📅 Schedule: (UTC)
  • Branch creation

    • At any time (no schedule defined)
  • Automerge

    • At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
  •  If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Footnotes
  1. Time when v0.69.4 release artifacts became publicly available. The malicious tag was pushed at ~17:43 UTC, triggering the release pipeline. ↩
  2. Earliest suspicious activity observed in our audit log. ↩↩2
@renovaterenovateBot
added

package:github-actions
Pull requests that update action deps
type:dependencies
Pull requests that update a dependency file
update:minor
Minor Updates of dependency
labels
Mar 24, 2026
@snyk-io
snyk-ioBot
commented
Mar 24, 2026•

edited

Loading

Copy link


Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.
StatusScan Engine Critical High Medium LowTotal (0)
✅Open Source Security0000 0 issues
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMar 27, 2026
@renovaterenovateBot
closed this
Mar 27, 2026
@renovate
renovateBot
deleted the

renovate/github-tags-aquasecurity-trivy-action-vulnerability

branch
March 27, 2026 01:57
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Mar 28, 2026
@renovaterenovateBot
reopened this
Mar 28, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
24158b3 to
8c3ea0aCompareMarch 28, 2026 01:05
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedApr 4, 2026
@renovaterenovateBot
closed this
Apr 4, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Apr 4, 2026
@renovaterenovateBot
reopened this
Apr 4, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
8c3ea0a to
58cfc9aCompareApril 4, 2026 20:54
@renovaterenovateBot
added
the 
status:ready-to-merge
PR is ready to merge, skips approving
label
Apr 18, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMay 1, 2026
@renovaterenovateBot
closed this
May 1, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]May 2, 2026
@renovaterenovateBot
reopened this
May 2, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
58cfc9a to
bc5d01cCompareMay 2, 2026 01:42
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 10, 2026
@renovaterenovateBot
closed this
Jul 10, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 10, 2026
@renovaterenovateBot
reopened this
Jul 10, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
bc5d01c to
1b9d045CompareJuly 10, 2026 19:13
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 16, 2026
@renovaterenovateBot
closed this
Jul 16, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 16, 2026
@renovaterenovateBot
reopened this
Jul 16, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
1b9d045 to
06294b3CompareJuly 16, 2026 15:06
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedAug 24, 2026
@renovaterenovateBot
closed this
Aug 24, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Aug 25, 2026
@renovaterenovateBot
reopened this
Aug 25, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
from
06294b3 to
004fe91CompareAugust 25, 2026 20:12
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

package:github-actionsPull requests that update action depsstatus:ready-to-mergePR is ready to merge, skips approvingtype:dependenciesPull requests that update a dependency fileupdate:minorMinor Updates of dependency

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - #145
Open
renovate[bot] wants to merge 1 commit into
devfrom 
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Open
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]#145
renovate[bot] wants to merge 1 commit into
devfrom 
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Conversation
@renovate
@renovaterenovateBot
commented
Mar 24, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
This PR contains the following updates:
PackageTypeUpdateChange
aquasecurity/trivy-actionactionminor0.33.1 → 0.35.0
Trivy Action has a script injection via sourced env file in composite action
CVE-2026-26189 / GHSA-9p44-j4g5-cfx5
More information
Details
Command Injection in aquasecurity/trivy-action via Unsanitized Environment Variable Export
A command injection vulnerability exists in aquasecurity/trivy-action due to improper handling of action inputs when exporting environment variables. The action writes export VAR=<input> lines to trivy_envs.txt based on user-supplied inputs and subsequently sources this file in entrypoint.sh.
Because input values are written without appropriate shell escaping, attacker-controlled input containing shell metacharacters (e.g., $(...), backticks, or other command substitution syntax) may be evaluated during the sourcing process. This can result in arbitrary command execution within the GitHub Actions runner context.
Severity:
Moderate
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
CWE-78: Improper Neutralization of Special Elements used in an OS Command (‘OS Command Injection’)
Impact:
Successful exploitation may lead to arbitrary command execution in the CI runner environment.
Affected Versions:
  • Versions >= 0.31.0 and <= 0.33.1
  • Introduced in commit 7aca5ac
Affected Conditions:
The vulnerability is exploitable when a consuming workflow passes attacker-controlled data into any action input that is written to trivy_envs.txt. Access to user input is required by the malicious actor.
A representative exploitation pattern involves incorporating untrusted pull request metadata into an action parameter. For example:
- uses: aquasecurity/trivy-action@0.33.1with:
output: "trivy-$.sarif"
If the pull request title contains shell syntax, it may be executed when the generated environment file is sourced.
Not Affected:
  • Workflows that do not pass attacker-controlled data into trivy-action inputs
  • Workflows that upgrade to a patched version that properly escapes shell values or eliminates the source ./trivy_envs.txt pattern
  • Workflows where user input is not accessible.
Call Sites:
  • action.yaml:188 — set_env_var_if_provided writes unescaped export lines
  • entrypoint.sh:9 — sources ./trivy_envs.txt
Severity
  • CVSS Score: 5.9 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Trivy ecosystem supply chain was briefly compromised
CVE-2026-33634 / GHSA-69fq-xp46-6x23
More information
Details
Summary
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.

On March 22, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.5 and v0.69.6 DockerHub images.
Exposure Window
ComponentStart (UTC)End (UTC)Duration
trivy v0.69.42026-03-19 18:22 12026-03-19 ~21:42~3 hours
trivy-action2026-03-19 ~17:43 22026-03-20 ~05:40~12 hours
setup-trivy2026-03-19 ~17:43 22026-03-19 ~21:44~4 hours
dockerhub trivy images v0.69.5 and v0.69.62026-03-22 15:432026-03-23 ~01:40~10 hours
Affected Components
Note that all malicious components, artifacts, commits, etc have been removed from all sources and destinations (yet they may linger in intermediary caches). Use this information to understand if you have been exposed to the malicious artifacts during the exposure window.
trivy binary and image
You are affected if you used:
  1. trivy binaries version v0.69.4 (or latest during the exposure window) distributed via GitHub, Deb, RPM.
  2. trivy container images v0.69.4 (or latest during the exposure window) distributed via GHCR, ECR public, Docker Hub.
  3. trivy container images v0.69.5 and v0.69.6 (or latest during the exposure window) distributed via Docker Hub.
You are not affected if you used:
  1. trivy (binary or image) version v0.69.3 or earlier.

    1. v0.69.3 is protected by GitHub's immutable releases feature (enabled March 3, before v0.69.3 was published).
    2. v0.69.2 predates immutable releases enablement but integrity can be verified via sigstore signatures (see "How to Verify" section below).
  2. trivy images referenced by digest.
  3. trivy binaries built from source.

    1. The malicious code was not committed to Trivy's main branch. It was fetched and built on the ephemeral runner, and also committed to a v0.70.0 branch but no release or git tag was ever pushed.
  4. homebrew from official formula (brew install trivy)

    1. The official homebrew formula is building trivy directly from source.
    2. There's an additional custom trivy tap which was compromised as part of the v0.69.4 release, but that tap requires special installation and is not even mentioned in the trivy documentation.
aquasecurity/trivy-action GitHub Action
You are affected if you used:
  1. Any tags prior except 0.35.0 (0.0.1 – 0.34.2) to reference the action.
  2. the action's version: latest parameter explicitly (not the default) during the trivy binary exposure window.
  3. SHA pinning to a commit prior to 2025-04-09.

    1. trivy-action started pinning setup-go with pull request trivy-action#456. If you pinned trivy-action to a commit prior to that PR (merged 2025-04-09), then you would get a safe trivy-action but it would get a malicious setup-trivy, if invoked during the setup-trivy exposure window.
You are not affected if you used:
  1. 0.35.0 tag

    1. 0.35.0 is protected by GitHub's immutable releases feature (enabled March 4, before 0.35.0 was published) and was not affected by the tag hijacking attack.
  2. SHA pinning to a safe commit commit after 2025-04-09.
aquasecurity/setup-trivy GitHub Action
You are affected if you used:
  1. Any version without pinning.
You are not affected if you used:
  1. SHA pinning to a safe commit.
Attack Details
Root Cause
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.
Trivy v0.69.4 binary and container images
The attacker created a malicious release by:
  1. Pushing a commit (1885610c) that swapped the actions/checkout reference to an imposter commit (70379aad) containing a composite action that downloaded malicious Go source files from a typosquatted domain
  2. Adding --skip=validate to goreleaser to bypass binary validation
  3. Tagging this commit as v0.69.4, triggering the release pipeline
The compromised release was distributed across Trivy's regular distribution channels channels: GHCR, ECR Public, Docker Hub (both 0.69.4 and latest tags), deb/rpm packages, and get.trivy.dev.
The attacker attempted to release a v0.70.0 malicious release but that was stopped prematurely.
trivy-action tag hijacking
The attacker force-pushed 76 of 77 version tags to malicious commits that injected an infostealer into entrypoint.sh. The malicious code executes before the legitimate Trivy scan and does the following:
  1. Dumps Runner.Worker process memory via /proc/<pid>/mem to extract secrets. Sweeps 50+ filesystem paths for SSH keys, AWS/GCP/Azure credentials, Kubernetes tokens, Docker configs, .env files, database credentials, and cryptocurrency wallets.
  2. Encrypts collected data using AES-256-CBC with RSA-4096 hybrid encryption.
  3. Transmits to attacker-controlled infrastructure. If exfiltration fails and INPUT_GITHUB_PAT is set, creates a public tpcp-docs repository on the victim's GitHub account and uploads stolen data as a release asset.
setup-trivy release replacement
All 7 existing tags (v0.2.0 – v0.2.6) were force-pushed to malicious commits. The malicious action.yaml contained the same infostealer as trivy-action, injected as a "Setup environment" step that executes before the legitimate Trivy installation.

We have removed all malicious releases within ~4 hours and re-created v0.2.6 with safe content. Tags v0.2.0 – v0.2.5 were not restored.
Trivy v0.69.5 and v0.69.6 docker image published.
The attacker created aquasec/trivy:0.69.5 and aquasec/trivy:0.69.6 with the same C2 domain as the v0.69.4 payload, and pushed them directly to Docker Hub using separately-compromised Docker Hub credentials (not via GitHub). No corresponding GitHub tags or releases existed.

We have removed all tags related to 0.69.5 and 0.69.6 and restored the latest tag to the safe 0.69.3 tag.
Recommended Actions
Update to Known-Safe Versions
ComponentSafe Version
Trivy binaryv0.69.2, v0.69.3
trivy-actionv0.35.0
setup-trivyv0.2.6
Regarding trivy-action: The original tags (0.0.1 – 0.34.2) were deleted during remediation. Because the attacker's force-push caused these tags to be treated as immutable releases by GitHub, they cannot be re-created with the same names. New tags have been published with a v prefix (v0.0.1 – v0.34.2) pointing to the original legitimate commits. Three tags: v0.0.10, v0.34.1, and v0.34.2 have not yet been restored. If you need to reference a version older than 0.35.0, use the v-prefixed tag (e.g., aquasecurity/trivy-action@v0.34.0 instead of @0.34.0).
Rotate All Potentially Exposed Secrets
Based on information shared above, if there is any possibility that a compromised version ran in your environment, all secrets accessible to affected pipelines must be treated as exposed and rotated immediately.
Audit Trivy Versions
Check whether your organization pulled or executed Trivy v0.69.4 from any source. Remove any affected artifacts immediately.
Audit GitHub Action References
Review all workflows using aquasecurity/trivy-action or aquasecurity/setup-trivy. Check workflow run logs from March 19–20, 2026 for signs of compromise.
Search for Exfiltration Artifacts
Look for repositories named tpcp-docs in your 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 SHA Hashes
Pin GitHub Actions to full, immutable commit SHA hashes, don't use mutable version tags. As described here: https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions
How to Verify Existing Installations
Binary verification
##### Download binary and sigstore bundle
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz"
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json"##### Verify signature
$ cosign verify-blob \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--bundle trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json \
trivy_0.69.2_Linux-64bit.tar.gz
Verified OK
##### Check signing timestamp
$ date -u -d @$(jq -r '.verificationMaterial.tlogEntries[].integratedTime' trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json)
Sat Mar 1 19:11:02 UTC 2026
##### ✅ Signed on Mar 1, before the attack on Mar 19
Container image verification
##### Verify signature and get image digest
$ cosign verify \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--new-bundle-format \
ghcr.io/aquasecurity/trivy:0.69.2
Verification for ghcr.io/aquasecurity/trivy:0.69.2 --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The code-signing certificate was verified using trusted certificate authority certificates
##### Get digest and check all signing timestamps via Rekor
$ DIGEST=$(cosign verify \ --certificate-identity-regexp 'https://github\.com/aquasecurity/' \ --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \ --new-bundle-format -o json ghcr.io/aquasecurity/trivy:0.69.2 2>/dev/null | \ jq -r '.[0].critical.image."docker-manifest-digest"')
$ rekor-cli search --sha "$DIGEST"| grep -v 'Found'|whileread uuid;do
rekor-cli get --uuid "$uuid"| grep IntegratedTime
done
IntegratedTime: 2026-03-01T19:13:52Z
IntegratedTime: 2026-03-01T19:13:47Z
IntegratedTime: 2026-03-01T19:13:57Z
IntegratedTime: 2026-03-01T19:13:54Z
IntegratedTime: 2026-03-01T19:13:46Z
IntegratedTime: 2026-03-01T19:13:37Z
##### ✅ All signed on Mar 1, before the attack on Mar 19
Indicators of Compromise
Executable binaries
SHA256Filename
c5b16c42dbd2a1494141cd651a406ec9094d5031a421c0aa624c4d139ae81239trivy_0.69.4_FreeBSD_64bit.tar.gz
cff74e3e9ac0cda2078d31800d8fcad832d7b52c9920b085054d1e96dacff8a3trivy_0.69.4_Linux-32bit.deb
55047c55a5ceab6d80b13884b4a4e8cd27a0bab7a218a952a00aae9e05f16f80trivy_0.69.4_Linux-32bit.rpm
ba04ba6a0c028cde17599c8ddaefdb854055c5a23c595e06630732002ea59a76trivy_0.69.4_Linux-32bit.tar.gz
0ca60dd18178d1c79d59cc06be12c540c121a4aea467484244667131aa13c311trivy_0.69.4_Linux-64bit.deb
a5696321a6c93071f46c8bb8cbd0a8d2bce6d1860cc3c109247a4e8b64ebd317trivy_0.69.4_Linux-64bit.rpm
385d498d18a3a7c67878ca7322716f9da25683eb1a4bf9e9592da0d5f2ab09f6trivy_0.69.4_Linux-64bit.tar.gz
8f0c7b92b251c61cbca2add06c676dd21fde8fbb2d0cd6616383fae29b21756atrivy_0.69.4_Linux-ARM.deb
c5df9d1bc6275711b2884a9ed4aacfe4e10dbe3c8f6c79df59126fd0e6dcd83ftrivy_0.69.4_Linux-ARM.rpm
f7a9bbfec8add36c548add4d875848b8b57c21fabe236d115f1c49113d12b332trivy_0.69.4_Linux-ARM.tar.gz
9a833d68a49ec6d44bc50fb9ff3b184bafb0edc913e1293daebe51d334676a70trivy_0.69.4_Linux-ARM64.deb
451ce0c4deb620894d07a2f4a37c8ea3b7a4f9b6d111651b4ac3bcc737b0fac0trivy_0.69.4_Linux-ARM64.rpm
e401ae1e6d2442fa9a0c79dc0f3b0457ecfebf74a9c0a920159c49437f663aeftrivy_0.69.4_Linux-ARM64.tar.gz
284622577cf6a7c58704de60194205f765fcef432934c200b462ef0290aa5f57trivy_0.69.4_Linux-PPC64LE.deb
5fac89e66d70cadec5c0e30c0b0cf8bf38c145cbf06422d40d076985195e1dd6trivy_0.69.4_Linux-PPC64LE.rpm
52518d441fd6dd25fa5126683a330592d3be80d5ce3fb9e0b1becb806ff4f857trivy_0.69.4_Linux-PPC64LE.tar.gz
62585efcdc7767f3fe0b9ae2897fe03bf331934492fd7a5da46f14fd7bf705c8trivy_0.69.4_Linux-s390x.deb
107be2081bdc3ddad2889ae037ab2ad6bbd214fb9a43eaa25390d00411d1c7ddtrivy_0.69.4_Linux-s390x.rpm
16c855c398a8b185a907790054b70164358844a893bf9965651b88d6967c7c0atrivy_0.69.4_Linux-s390x.tar.gz
90d61cf37355b89fae9ff84867100e1721c1876007ef1771e465ce5a721141adtrivy_0.69.4_macOS-64bit.tar.gz
1dc871b02cd7a1fd80babb1b8762a2fd9cc2b735d4d3759d012626de3ccc7a5btrivy_0.69.4_macOS-ARM64.tar.gz
0376b98064636c30f5fbe60fb3b1225516e23e88dd7e909937f81d9265292e7dtrivy_0.69.4_windows_64bit.zip
822dd269ec10459572dfaaefe163dae693c344249a0161953f0d5cdd110bd2a0trivy_0.69.4_linux_amd64
e64e152afe2c722d750f10259626f357cdea40420c5eedae37969fbf13abbecftrivy_0.69.4_linux_arm64
d5edd791021b966fb6af0ace09319ace7b97d6642363ef27b3d5056ca654a94ctrivy_0.69.4_s390x
ecce7ae5ffc9f57bb70efd3ea136a2923f701334a8cd47d4fbf01a97fd22859ctrivy_0.69.4_ppc64le
Container images (v0.69.4)
DigestTag
sha256:27f446230c60bbf0b70e008db798bd4f33b7826f9f76f756606f5417100beef30.69.4
sha256:12c702212dee1cbec9471e9261501a3335963321fe76e60e5a715b5acd3c40a20.69.4-linux/amd64
sha256:2d7cee41048988eec27615412e7c6e2e21046f2b5faa888c24e11ca6764058ed0.69.4-linux/arm64
sha256:ae3494bd6ae860d7727116681bd09fc7b20dc994ec7a8105738f0a623ea934270.69.4-linux/ppc64le
sha256:43f46547efd488e56dcf862ed4d7cc342730a803f8d5bec5cac443028fefabef0.69.4- linux/s390x
sha256:cc464a3961e1dbe145c75343b55c2f446e08b821782ec993728c4222b0d855890.69.4-signature
sha256:5aaa1d7cfa9ca4649d6ffad165435c519dc836fa6e21b729a2174ad10b057d2b0.69.5
sha256:95ff680103570179feb0c6667a9b9b2d98c53fa5a9a451265036810390bbe70a0.69.5-linux/arm64
sha256:4f7a06bb51714713ab308d2f8125f3b09ee1c3ffbba1a5ffd0cc80da95fbb6cc0.69.5-linux/ppc64le
sha256:edef8e5816eced552a909b878ff262c0c47776d3297bcc23796ad4cce1e854140.69.5-linux/s390x
sha256:425cd3e1a2846ac73944e891250377d2b03653e6f028833e30fc00c1abbc6d330.69.6
sha256:dd8beb3b40df080b3fd7f9a0f5a1b02f3692f65c68980f46da8328ce8bb788ef0.69.6-linux/amd64
sha256:4b22cedea58780ff76735c3e08b9ee8cb5d06c908ffa868152f11d45349eb6960.69.6-linux/arm64
sha256:9efd59534d2b6b81b8b7a0eeb3ad0e74015f358650e24b9dab00c900d31185930.69.6-linux/ppc64le
sha256:5e5fb53cf4ce5555171ff5206302ba2f4f66f5381bbf673c354c87a925473f070.69.6-linux/s390x
Network
C2/sinks:
  • scan.aquasecurtiy.org
  • 45.148.10.212
GitHub Repositories
Public repo on victim's GitHub account with tpcp-docs- prefix.

Stolen data uploaded as a release asset with tag data-<timestamp>.
Severity
  • CVSS Score: 9.4 / 10 (Critical)
  • 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
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
aquasecurity/trivy-action (aquasecurity/trivy-action)
v0.35.0: Release: v0.35.0
Compare Source
This release is a duplicate of 0.35.0 which was not compromised.
As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.
We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.
If you are currently using 0.35.0, your workflows are safe — no action is required.
v0.35.0: Release: v0.35.0
Compare Source
This release is a duplicate of 0.35.0 which was not compromised.
As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.
We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.
If you are currently using 0.35.0, your workflows are safe — no action is required.
v0.34.0: Release: v0.34.0
Compare Source
Full Changelog: aquasecurity/trivy-action@v0.33.1...v0.34.0
Configuration
📅 Schedule: (UTC)
  • Branch creation

    • At any time (no schedule defined)
  • Automerge

    • At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
  •  If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Footnotes
  1. Time when v0.69.4 release artifacts became publicly available. The malicious tag was pushed at ~17:43 UTC, triggering the release pipeline. ↩
  2. Earliest suspicious activity observed in our audit log. ↩↩2
@renovaterenovateBot
added

package:github-actions
Pull requests that update action deps
type:dependencies
Pull requests that update a dependency file
update:minor
Minor Updates of dependency
labels
Mar 24, 2026
@snyk-io
snyk-ioBot
commented
Mar 24, 2026•

edited

Loading

Copy link


Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.
StatusScan Engine Critical High Medium LowTotal (0)
✅Open Source Security0000 0 issues
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMar 27, 2026
@renovaterenovateBot
closed this
Mar 27, 2026
@renovate
renovateBot
deleted the

renovate/github-tags-aquasecurity-trivy-action-vulnerability

branch
March 27, 2026 01:57
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Mar 28, 2026
@renovaterenovateBot
reopened this
Mar 28, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
24158b3 to
8c3ea0aCompareMarch 28, 2026 01:05
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedApr 4, 2026
@renovaterenovateBot
closed this
Apr 4, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Apr 4, 2026
@renovaterenovateBot
reopened this
Apr 4, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
8c3ea0a to
58cfc9aCompareApril 4, 2026 20:54
@renovaterenovateBot
added
the 
status:ready-to-merge
PR is ready to merge, skips approving
label
Apr 18, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMay 1, 2026
@renovaterenovateBot
closed this
May 1, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]May 2, 2026
@renovaterenovateBot
reopened this
May 2, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
58cfc9a to
bc5d01cCompareMay 2, 2026 01:42
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 10, 2026
@renovaterenovateBot
closed this
Jul 10, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 10, 2026
@renovaterenovateBot
reopened this
Jul 10, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
bc5d01c to
1b9d045CompareJuly 10, 2026 19:13
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 16, 2026
@renovaterenovateBot
closed this
Jul 16, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 16, 2026
@renovaterenovateBot
reopened this
Jul 16, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
1b9d045 to
06294b3CompareJuly 16, 2026 15:06
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedAug 24, 2026
@renovaterenovateBot
closed this
Aug 24, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Aug 25, 2026
@renovaterenovateBot
reopened this
Aug 25, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
from
06294b3 to
004fe91CompareAugust 25, 2026 20:12
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

package:github-actionsPull requests that update action depsstatus:ready-to-mergePR is ready to merge, skips approvingtype:dependenciesPull requests that update a dependency fileupdate:minorMinor Updates of dependency

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - #145
Open
renovate[bot] wants to merge 1 commit into
devfrom 
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Open
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]#145
renovate[bot] wants to merge 1 commit into
devfrom 
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Conversation
@renovate
@renovaterenovateBot
commented
Mar 24, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
This PR contains the following updates:
PackageTypeUpdateChange
aquasecurity/trivy-actionactionminor0.33.1 → 0.35.0
Trivy Action has a script injection via sourced env file in composite action
CVE-2026-26189 / GHSA-9p44-j4g5-cfx5
More information
Details
Command Injection in aquasecurity/trivy-action via Unsanitized Environment Variable Export
A command injection vulnerability exists in aquasecurity/trivy-action due to improper handling of action inputs when exporting environment variables. The action writes export VAR=<input> lines to trivy_envs.txt based on user-supplied inputs and subsequently sources this file in entrypoint.sh.
Because input values are written without appropriate shell escaping, attacker-controlled input containing shell metacharacters (e.g., $(...), backticks, or other command substitution syntax) may be evaluated during the sourcing process. This can result in arbitrary command execution within the GitHub Actions runner context.
Severity:
Moderate
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
CWE-78: Improper Neutralization of Special Elements used in an OS Command (‘OS Command Injection’)
Impact:
Successful exploitation may lead to arbitrary command execution in the CI runner environment.
Affected Versions:
  • Versions >= 0.31.0 and <= 0.33.1
  • Introduced in commit 7aca5ac
Affected Conditions:
The vulnerability is exploitable when a consuming workflow passes attacker-controlled data into any action input that is written to trivy_envs.txt. Access to user input is required by the malicious actor.
A representative exploitation pattern involves incorporating untrusted pull request metadata into an action parameter. For example:
- uses: aquasecurity/trivy-action@0.33.1with:
output: "trivy-$.sarif"
If the pull request title contains shell syntax, it may be executed when the generated environment file is sourced.
Not Affected:
  • Workflows that do not pass attacker-controlled data into trivy-action inputs
  • Workflows that upgrade to a patched version that properly escapes shell values or eliminates the source ./trivy_envs.txt pattern
  • Workflows where user input is not accessible.
Call Sites:
  • action.yaml:188 — set_env_var_if_provided writes unescaped export lines
  • entrypoint.sh:9 — sources ./trivy_envs.txt
Severity
  • CVSS Score: 5.9 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Trivy ecosystem supply chain was briefly compromised
CVE-2026-33634 / GHSA-69fq-xp46-6x23
More information
Details
Summary
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.

On March 22, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.5 and v0.69.6 DockerHub images.
Exposure Window
ComponentStart (UTC)End (UTC)Duration
trivy v0.69.42026-03-19 18:22 12026-03-19 ~21:42~3 hours
trivy-action2026-03-19 ~17:43 22026-03-20 ~05:40~12 hours
setup-trivy2026-03-19 ~17:43 22026-03-19 ~21:44~4 hours
dockerhub trivy images v0.69.5 and v0.69.62026-03-22 15:432026-03-23 ~01:40~10 hours
Affected Components
Note that all malicious components, artifacts, commits, etc have been removed from all sources and destinations (yet they may linger in intermediary caches). Use this information to understand if you have been exposed to the malicious artifacts during the exposure window.
trivy binary and image
You are affected if you used:
  1. trivy binaries version v0.69.4 (or latest during the exposure window) distributed via GitHub, Deb, RPM.
  2. trivy container images v0.69.4 (or latest during the exposure window) distributed via GHCR, ECR public, Docker Hub.
  3. trivy container images v0.69.5 and v0.69.6 (or latest during the exposure window) distributed via Docker Hub.
You are not affected if you used:
  1. trivy (binary or image) version v0.69.3 or earlier.

    1. v0.69.3 is protected by GitHub's immutable releases feature (enabled March 3, before v0.69.3 was published).
    2. v0.69.2 predates immutable releases enablement but integrity can be verified via sigstore signatures (see "How to Verify" section below).
  2. trivy images referenced by digest.
  3. trivy binaries built from source.

    1. The malicious code was not committed to Trivy's main branch. It was fetched and built on the ephemeral runner, and also committed to a v0.70.0 branch but no release or git tag was ever pushed.
  4. homebrew from official formula (brew install trivy)

    1. The official homebrew formula is building trivy directly from source.
    2. There's an additional custom trivy tap which was compromised as part of the v0.69.4 release, but that tap requires special installation and is not even mentioned in the trivy documentation.
aquasecurity/trivy-action GitHub Action
You are affected if you used:
  1. Any tags prior except 0.35.0 (0.0.1 – 0.34.2) to reference the action.
  2. the action's version: latest parameter explicitly (not the default) during the trivy binary exposure window.
  3. SHA pinning to a commit prior to 2025-04-09.

    1. trivy-action started pinning setup-go with pull request trivy-action#456. If you pinned trivy-action to a commit prior to that PR (merged 2025-04-09), then you would get a safe trivy-action but it would get a malicious setup-trivy, if invoked during the setup-trivy exposure window.
You are not affected if you used:
  1. 0.35.0 tag

    1. 0.35.0 is protected by GitHub's immutable releases feature (enabled March 4, before 0.35.0 was published) and was not affected by the tag hijacking attack.
  2. SHA pinning to a safe commit commit after 2025-04-09.
aquasecurity/setup-trivy GitHub Action
You are affected if you used:
  1. Any version without pinning.
You are not affected if you used:
  1. SHA pinning to a safe commit.
Attack Details
Root Cause
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.
Trivy v0.69.4 binary and container images
The attacker created a malicious release by:
  1. Pushing a commit (1885610c) that swapped the actions/checkout reference to an imposter commit (70379aad) containing a composite action that downloaded malicious Go source files from a typosquatted domain
  2. Adding --skip=validate to goreleaser to bypass binary validation
  3. Tagging this commit as v0.69.4, triggering the release pipeline
The compromised release was distributed across Trivy's regular distribution channels channels: GHCR, ECR Public, Docker Hub (both 0.69.4 and latest tags), deb/rpm packages, and get.trivy.dev.
The attacker attempted to release a v0.70.0 malicious release but that was stopped prematurely.
trivy-action tag hijacking
The attacker force-pushed 76 of 77 version tags to malicious commits that injected an infostealer into entrypoint.sh. The malicious code executes before the legitimate Trivy scan and does the following:
  1. Dumps Runner.Worker process memory via /proc/<pid>/mem to extract secrets. Sweeps 50+ filesystem paths for SSH keys, AWS/GCP/Azure credentials, Kubernetes tokens, Docker configs, .env files, database credentials, and cryptocurrency wallets.
  2. Encrypts collected data using AES-256-CBC with RSA-4096 hybrid encryption.
  3. Transmits to attacker-controlled infrastructure. If exfiltration fails and INPUT_GITHUB_PAT is set, creates a public tpcp-docs repository on the victim's GitHub account and uploads stolen data as a release asset.
setup-trivy release replacement
All 7 existing tags (v0.2.0 – v0.2.6) were force-pushed to malicious commits. The malicious action.yaml contained the same infostealer as trivy-action, injected as a "Setup environment" step that executes before the legitimate Trivy installation.

We have removed all malicious releases within ~4 hours and re-created v0.2.6 with safe content. Tags v0.2.0 – v0.2.5 were not restored.
Trivy v0.69.5 and v0.69.6 docker image published.
The attacker created aquasec/trivy:0.69.5 and aquasec/trivy:0.69.6 with the same C2 domain as the v0.69.4 payload, and pushed them directly to Docker Hub using separately-compromised Docker Hub credentials (not via GitHub). No corresponding GitHub tags or releases existed.

We have removed all tags related to 0.69.5 and 0.69.6 and restored the latest tag to the safe 0.69.3 tag.
Recommended Actions
Update to Known-Safe Versions
ComponentSafe Version
Trivy binaryv0.69.2, v0.69.3
trivy-actionv0.35.0
setup-trivyv0.2.6
Regarding trivy-action: The original tags (0.0.1 – 0.34.2) were deleted during remediation. Because the attacker's force-push caused these tags to be treated as immutable releases by GitHub, they cannot be re-created with the same names. New tags have been published with a v prefix (v0.0.1 – v0.34.2) pointing to the original legitimate commits. Three tags: v0.0.10, v0.34.1, and v0.34.2 have not yet been restored. If you need to reference a version older than 0.35.0, use the v-prefixed tag (e.g., aquasecurity/trivy-action@v0.34.0 instead of @0.34.0).
Rotate All Potentially Exposed Secrets
Based on information shared above, if there is any possibility that a compromised version ran in your environment, all secrets accessible to affected pipelines must be treated as exposed and rotated immediately.
Audit Trivy Versions
Check whether your organization pulled or executed Trivy v0.69.4 from any source. Remove any affected artifacts immediately.
Audit GitHub Action References
Review all workflows using aquasecurity/trivy-action or aquasecurity/setup-trivy. Check workflow run logs from March 19–20, 2026 for signs of compromise.
Search for Exfiltration Artifacts
Look for repositories named tpcp-docs in your 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 SHA Hashes
Pin GitHub Actions to full, immutable commit SHA hashes, don't use mutable version tags. As described here: https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions
How to Verify Existing Installations
Binary verification
##### Download binary and sigstore bundle
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz"
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json"##### Verify signature
$ cosign verify-blob \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--bundle trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json \
trivy_0.69.2_Linux-64bit.tar.gz
Verified OK
##### Check signing timestamp
$ date -u -d @$(jq -r '.verificationMaterial.tlogEntries[].integratedTime' trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json)
Sat Mar 1 19:11:02 UTC 2026
##### ✅ Signed on Mar 1, before the attack on Mar 19
Container image verification
##### Verify signature and get image digest
$ cosign verify \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--new-bundle-format \
ghcr.io/aquasecurity/trivy:0.69.2
Verification for ghcr.io/aquasecurity/trivy:0.69.2 --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The code-signing certificate was verified using trusted certificate authority certificates
##### Get digest and check all signing timestamps via Rekor
$ DIGEST=$(cosign verify \ --certificate-identity-regexp 'https://github\.com/aquasecurity/' \ --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \ --new-bundle-format -o json ghcr.io/aquasecurity/trivy:0.69.2 2>/dev/null | \ jq -r '.[0].critical.image."docker-manifest-digest"')
$ rekor-cli search --sha "$DIGEST"| grep -v 'Found'|whileread uuid;do
rekor-cli get --uuid "$uuid"| grep IntegratedTime
done
IntegratedTime: 2026-03-01T19:13:52Z
IntegratedTime: 2026-03-01T19:13:47Z
IntegratedTime: 2026-03-01T19:13:57Z
IntegratedTime: 2026-03-01T19:13:54Z
IntegratedTime: 2026-03-01T19:13:46Z
IntegratedTime: 2026-03-01T19:13:37Z
##### ✅ All signed on Mar 1, before the attack on Mar 19
Indicators of Compromise
Executable binaries
SHA256Filename
c5b16c42dbd2a1494141cd651a406ec9094d5031a421c0aa624c4d139ae81239trivy_0.69.4_FreeBSD_64bit.tar.gz
cff74e3e9ac0cda2078d31800d8fcad832d7b52c9920b085054d1e96dacff8a3trivy_0.69.4_Linux-32bit.deb
55047c55a5ceab6d80b13884b4a4e8cd27a0bab7a218a952a00aae9e05f16f80trivy_0.69.4_Linux-32bit.rpm
ba04ba6a0c028cde17599c8ddaefdb854055c5a23c595e06630732002ea59a76trivy_0.69.4_Linux-32bit.tar.gz
0ca60dd18178d1c79d59cc06be12c540c121a4aea467484244667131aa13c311trivy_0.69.4_Linux-64bit.deb
a5696321a6c93071f46c8bb8cbd0a8d2bce6d1860cc3c109247a4e8b64ebd317trivy_0.69.4_Linux-64bit.rpm
385d498d18a3a7c67878ca7322716f9da25683eb1a4bf9e9592da0d5f2ab09f6trivy_0.69.4_Linux-64bit.tar.gz
8f0c7b92b251c61cbca2add06c676dd21fde8fbb2d0cd6616383fae29b21756atrivy_0.69.4_Linux-ARM.deb
c5df9d1bc6275711b2884a9ed4aacfe4e10dbe3c8f6c79df59126fd0e6dcd83ftrivy_0.69.4_Linux-ARM.rpm
f7a9bbfec8add36c548add4d875848b8b57c21fabe236d115f1c49113d12b332trivy_0.69.4_Linux-ARM.tar.gz
9a833d68a49ec6d44bc50fb9ff3b184bafb0edc913e1293daebe51d334676a70trivy_0.69.4_Linux-ARM64.deb
451ce0c4deb620894d07a2f4a37c8ea3b7a4f9b6d111651b4ac3bcc737b0fac0trivy_0.69.4_Linux-ARM64.rpm
e401ae1e6d2442fa9a0c79dc0f3b0457ecfebf74a9c0a920159c49437f663aeftrivy_0.69.4_Linux-ARM64.tar.gz
284622577cf6a7c58704de60194205f765fcef432934c200b462ef0290aa5f57trivy_0.69.4_Linux-PPC64LE.deb
5fac89e66d70cadec5c0e30c0b0cf8bf38c145cbf06422d40d076985195e1dd6trivy_0.69.4_Linux-PPC64LE.rpm
52518d441fd6dd25fa5126683a330592d3be80d5ce3fb9e0b1becb806ff4f857trivy_0.69.4_Linux-PPC64LE.tar.gz
62585efcdc7767f3fe0b9ae2897fe03bf331934492fd7a5da46f14fd7bf705c8trivy_0.69.4_Linux-s390x.deb
107be2081bdc3ddad2889ae037ab2ad6bbd214fb9a43eaa25390d00411d1c7ddtrivy_0.69.4_Linux-s390x.rpm
16c855c398a8b185a907790054b70164358844a893bf9965651b88d6967c7c0atrivy_0.69.4_Linux-s390x.tar.gz
90d61cf37355b89fae9ff84867100e1721c1876007ef1771e465ce5a721141adtrivy_0.69.4_macOS-64bit.tar.gz
1dc871b02cd7a1fd80babb1b8762a2fd9cc2b735d4d3759d012626de3ccc7a5btrivy_0.69.4_macOS-ARM64.tar.gz
0376b98064636c30f5fbe60fb3b1225516e23e88dd7e909937f81d9265292e7dtrivy_0.69.4_windows_64bit.zip
822dd269ec10459572dfaaefe163dae693c344249a0161953f0d5cdd110bd2a0trivy_0.69.4_linux_amd64
e64e152afe2c722d750f10259626f357cdea40420c5eedae37969fbf13abbecftrivy_0.69.4_linux_arm64
d5edd791021b966fb6af0ace09319ace7b97d6642363ef27b3d5056ca654a94ctrivy_0.69.4_s390x
ecce7ae5ffc9f57bb70efd3ea136a2923f701334a8cd47d4fbf01a97fd22859ctrivy_0.69.4_ppc64le
Container images (v0.69.4)
DigestTag
sha256:27f446230c60bbf0b70e008db798bd4f33b7826f9f76f756606f5417100beef30.69.4
sha256:12c702212dee1cbec9471e9261501a3335963321fe76e60e5a715b5acd3c40a20.69.4-linux/amd64
sha256:2d7cee41048988eec27615412e7c6e2e21046f2b5faa888c24e11ca6764058ed0.69.4-linux/arm64
sha256:ae3494bd6ae860d7727116681bd09fc7b20dc994ec7a8105738f0a623ea934270.69.4-linux/ppc64le
sha256:43f46547efd488e56dcf862ed4d7cc342730a803f8d5bec5cac443028fefabef0.69.4- linux/s390x
sha256:cc464a3961e1dbe145c75343b55c2f446e08b821782ec993728c4222b0d855890.69.4-signature
sha256:5aaa1d7cfa9ca4649d6ffad165435c519dc836fa6e21b729a2174ad10b057d2b0.69.5
sha256:95ff680103570179feb0c6667a9b9b2d98c53fa5a9a451265036810390bbe70a0.69.5-linux/arm64
sha256:4f7a06bb51714713ab308d2f8125f3b09ee1c3ffbba1a5ffd0cc80da95fbb6cc0.69.5-linux/ppc64le
sha256:edef8e5816eced552a909b878ff262c0c47776d3297bcc23796ad4cce1e854140.69.5-linux/s390x
sha256:425cd3e1a2846ac73944e891250377d2b03653e6f028833e30fc00c1abbc6d330.69.6
sha256:dd8beb3b40df080b3fd7f9a0f5a1b02f3692f65c68980f46da8328ce8bb788ef0.69.6-linux/amd64
sha256:4b22cedea58780ff76735c3e08b9ee8cb5d06c908ffa868152f11d45349eb6960.69.6-linux/arm64
sha256:9efd59534d2b6b81b8b7a0eeb3ad0e74015f358650e24b9dab00c900d31185930.69.6-linux/ppc64le
sha256:5e5fb53cf4ce5555171ff5206302ba2f4f66f5381bbf673c354c87a925473f070.69.6-linux/s390x
Network
C2/sinks:
  • scan.aquasecurtiy.org
  • 45.148.10.212
GitHub Repositories
Public repo on victim's GitHub account with tpcp-docs- prefix.

Stolen data uploaded as a release asset with tag data-<timestamp>.
Severity
  • CVSS Score: 9.4 / 10 (Critical)
  • 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
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
aquasecurity/trivy-action (aquasecurity/trivy-action)
v0.35.0: Release: v0.35.0
Compare Source
This release is a duplicate of 0.35.0 which was not compromised.
As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.
We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.
If you are currently using 0.35.0, your workflows are safe — no action is required.
v0.35.0: Release: v0.35.0
Compare Source
This release is a duplicate of 0.35.0 which was not compromised.
As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.
We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.
If you are currently using 0.35.0, your workflows are safe — no action is required.
v0.34.0: Release: v0.34.0
Compare Source
Full Changelog: aquasecurity/trivy-action@v0.33.1...v0.34.0
Configuration
📅 Schedule: (UTC)
  • Branch creation

    • At any time (no schedule defined)
  • Automerge

    • At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
  •  If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Footnotes
  1. Time when v0.69.4 release artifacts became publicly available. The malicious tag was pushed at ~17:43 UTC, triggering the release pipeline. ↩
  2. Earliest suspicious activity observed in our audit log. ↩↩2
@renovaterenovateBot
added

package:github-actions
Pull requests that update action deps
type:dependencies
Pull requests that update a dependency file
update:minor
Minor Updates of dependency
labels
Mar 24, 2026
@snyk-io
snyk-ioBot
commented
Mar 24, 2026•

edited

Loading

Copy link


Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.
StatusScan Engine Critical High Medium LowTotal (0)
✅Open Source Security0000 0 issues
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMar 27, 2026
@renovaterenovateBot
closed this
Mar 27, 2026
@renovate
renovateBot
deleted the

renovate/github-tags-aquasecurity-trivy-action-vulnerability

branch
March 27, 2026 01:57
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Mar 28, 2026
@renovaterenovateBot
reopened this
Mar 28, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
24158b3 to
8c3ea0aCompareMarch 28, 2026 01:05
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedApr 4, 2026
@renovaterenovateBot
closed this
Apr 4, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Apr 4, 2026
@renovaterenovateBot
reopened this
Apr 4, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
8c3ea0a to
58cfc9aCompareApril 4, 2026 20:54
@renovaterenovateBot
added
the 
status:ready-to-merge
PR is ready to merge, skips approving
label
Apr 18, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMay 1, 2026
@renovaterenovateBot
closed this
May 1, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]May 2, 2026
@renovaterenovateBot
reopened this
May 2, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
58cfc9a to
bc5d01cCompareMay 2, 2026 01:42
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 10, 2026
@renovaterenovateBot
closed this
Jul 10, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 10, 2026
@renovaterenovateBot
reopened this
Jul 10, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
bc5d01c to
1b9d045CompareJuly 10, 2026 19:13
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 16, 2026
@renovaterenovateBot
closed this
Jul 16, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 16, 2026
@renovaterenovateBot
reopened this
Jul 16, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
1b9d045 to
06294b3CompareJuly 16, 2026 15:06
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedAug 24, 2026
@renovaterenovateBot
closed this
Aug 24, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Aug 25, 2026
@renovaterenovateBot
reopened this
Aug 25, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
from
06294b3 to
004fe91CompareAugust 25, 2026 20:12
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

package:github-actionsPull requests that update action depsstatus:ready-to-mergePR is ready to merge, skips approvingtype:dependenciesPull requests that update a dependency fileupdate:minorMinor Updates of dependency

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - #145
Open
renovate[bot] wants to merge 1 commit into
devfrom 
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Open
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]#145
renovate[bot] wants to merge 1 commit into
devfrom 
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Conversation
@renovate
@renovaterenovateBot
commented
Mar 24, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
This PR contains the following updates:
PackageTypeUpdateChange
aquasecurity/trivy-actionactionminor0.33.1 → 0.35.0
Trivy Action has a script injection via sourced env file in composite action
CVE-2026-26189 / GHSA-9p44-j4g5-cfx5
More information
Details
Command Injection in aquasecurity/trivy-action via Unsanitized Environment Variable Export
A command injection vulnerability exists in aquasecurity/trivy-action due to improper handling of action inputs when exporting environment variables. The action writes export VAR=<input> lines to trivy_envs.txt based on user-supplied inputs and subsequently sources this file in entrypoint.sh.
Because input values are written without appropriate shell escaping, attacker-controlled input containing shell metacharacters (e.g., $(...), backticks, or other command substitution syntax) may be evaluated during the sourcing process. This can result in arbitrary command execution within the GitHub Actions runner context.
Severity:
Moderate
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
CWE-78: Improper Neutralization of Special Elements used in an OS Command (‘OS Command Injection’)
Impact:
Successful exploitation may lead to arbitrary command execution in the CI runner environment.
Affected Versions:
  • Versions >= 0.31.0 and <= 0.33.1
  • Introduced in commit 7aca5ac
Affected Conditions:
The vulnerability is exploitable when a consuming workflow passes attacker-controlled data into any action input that is written to trivy_envs.txt. Access to user input is required by the malicious actor.
A representative exploitation pattern involves incorporating untrusted pull request metadata into an action parameter. For example:
- uses: aquasecurity/trivy-action@0.33.1with:
output: "trivy-$.sarif"
If the pull request title contains shell syntax, it may be executed when the generated environment file is sourced.
Not Affected:
  • Workflows that do not pass attacker-controlled data into trivy-action inputs
  • Workflows that upgrade to a patched version that properly escapes shell values or eliminates the source ./trivy_envs.txt pattern
  • Workflows where user input is not accessible.
Call Sites:
  • action.yaml:188 — set_env_var_if_provided writes unescaped export lines
  • entrypoint.sh:9 — sources ./trivy_envs.txt
Severity
  • CVSS Score: 5.9 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Trivy ecosystem supply chain was briefly compromised
CVE-2026-33634 / GHSA-69fq-xp46-6x23
More information
Details
Summary
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.

On March 22, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.5 and v0.69.6 DockerHub images.
Exposure Window
ComponentStart (UTC)End (UTC)Duration
trivy v0.69.42026-03-19 18:22 12026-03-19 ~21:42~3 hours
trivy-action2026-03-19 ~17:43 22026-03-20 ~05:40~12 hours
setup-trivy2026-03-19 ~17:43 22026-03-19 ~21:44~4 hours
dockerhub trivy images v0.69.5 and v0.69.62026-03-22 15:432026-03-23 ~01:40~10 hours
Affected Components
Note that all malicious components, artifacts, commits, etc have been removed from all sources and destinations (yet they may linger in intermediary caches). Use this information to understand if you have been exposed to the malicious artifacts during the exposure window.
trivy binary and image
You are affected if you used:
  1. trivy binaries version v0.69.4 (or latest during the exposure window) distributed via GitHub, Deb, RPM.
  2. trivy container images v0.69.4 (or latest during the exposure window) distributed via GHCR, ECR public, Docker Hub.
  3. trivy container images v0.69.5 and v0.69.6 (or latest during the exposure window) distributed via Docker Hub.
You are not affected if you used:
  1. trivy (binary or image) version v0.69.3 or earlier.

    1. v0.69.3 is protected by GitHub's immutable releases feature (enabled March 3, before v0.69.3 was published).
    2. v0.69.2 predates immutable releases enablement but integrity can be verified via sigstore signatures (see "How to Verify" section below).
  2. trivy images referenced by digest.
  3. trivy binaries built from source.

    1. The malicious code was not committed to Trivy's main branch. It was fetched and built on the ephemeral runner, and also committed to a v0.70.0 branch but no release or git tag was ever pushed.
  4. homebrew from official formula (brew install trivy)

    1. The official homebrew formula is building trivy directly from source.
    2. There's an additional custom trivy tap which was compromised as part of the v0.69.4 release, but that tap requires special installation and is not even mentioned in the trivy documentation.
aquasecurity/trivy-action GitHub Action
You are affected if you used:
  1. Any tags prior except 0.35.0 (0.0.1 – 0.34.2) to reference the action.
  2. the action's version: latest parameter explicitly (not the default) during the trivy binary exposure window.
  3. SHA pinning to a commit prior to 2025-04-09.

    1. trivy-action started pinning setup-go with pull request trivy-action#456. If you pinned trivy-action to a commit prior to that PR (merged 2025-04-09), then you would get a safe trivy-action but it would get a malicious setup-trivy, if invoked during the setup-trivy exposure window.
You are not affected if you used:
  1. 0.35.0 tag

    1. 0.35.0 is protected by GitHub's immutable releases feature (enabled March 4, before 0.35.0 was published) and was not affected by the tag hijacking attack.
  2. SHA pinning to a safe commit commit after 2025-04-09.
aquasecurity/setup-trivy GitHub Action
You are affected if you used:
  1. Any version without pinning.
You are not affected if you used:
  1. SHA pinning to a safe commit.
Attack Details
Root Cause
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.
Trivy v0.69.4 binary and container images
The attacker created a malicious release by:
  1. Pushing a commit (1885610c) that swapped the actions/checkout reference to an imposter commit (70379aad) containing a composite action that downloaded malicious Go source files from a typosquatted domain
  2. Adding --skip=validate to goreleaser to bypass binary validation
  3. Tagging this commit as v0.69.4, triggering the release pipeline
The compromised release was distributed across Trivy's regular distribution channels channels: GHCR, ECR Public, Docker Hub (both 0.69.4 and latest tags), deb/rpm packages, and get.trivy.dev.
The attacker attempted to release a v0.70.0 malicious release but that was stopped prematurely.
trivy-action tag hijacking
The attacker force-pushed 76 of 77 version tags to malicious commits that injected an infostealer into entrypoint.sh. The malicious code executes before the legitimate Trivy scan and does the following:
  1. Dumps Runner.Worker process memory via /proc/<pid>/mem to extract secrets. Sweeps 50+ filesystem paths for SSH keys, AWS/GCP/Azure credentials, Kubernetes tokens, Docker configs, .env files, database credentials, and cryptocurrency wallets.
  2. Encrypts collected data using AES-256-CBC with RSA-4096 hybrid encryption.
  3. Transmits to attacker-controlled infrastructure. If exfiltration fails and INPUT_GITHUB_PAT is set, creates a public tpcp-docs repository on the victim's GitHub account and uploads stolen data as a release asset.
setup-trivy release replacement
All 7 existing tags (v0.2.0 – v0.2.6) were force-pushed to malicious commits. The malicious action.yaml contained the same infostealer as trivy-action, injected as a "Setup environment" step that executes before the legitimate Trivy installation.

We have removed all malicious releases within ~4 hours and re-created v0.2.6 with safe content. Tags v0.2.0 – v0.2.5 were not restored.
Trivy v0.69.5 and v0.69.6 docker image published.
The attacker created aquasec/trivy:0.69.5 and aquasec/trivy:0.69.6 with the same C2 domain as the v0.69.4 payload, and pushed them directly to Docker Hub using separately-compromised Docker Hub credentials (not via GitHub). No corresponding GitHub tags or releases existed.

We have removed all tags related to 0.69.5 and 0.69.6 and restored the latest tag to the safe 0.69.3 tag.
Recommended Actions
Update to Known-Safe Versions
ComponentSafe Version
Trivy binaryv0.69.2, v0.69.3
trivy-actionv0.35.0
setup-trivyv0.2.6
Regarding trivy-action: The original tags (0.0.1 – 0.34.2) were deleted during remediation. Because the attacker's force-push caused these tags to be treated as immutable releases by GitHub, they cannot be re-created with the same names. New tags have been published with a v prefix (v0.0.1 – v0.34.2) pointing to the original legitimate commits. Three tags: v0.0.10, v0.34.1, and v0.34.2 have not yet been restored. If you need to reference a version older than 0.35.0, use the v-prefixed tag (e.g., aquasecurity/trivy-action@v0.34.0 instead of @0.34.0).
Rotate All Potentially Exposed Secrets
Based on information shared above, if there is any possibility that a compromised version ran in your environment, all secrets accessible to affected pipelines must be treated as exposed and rotated immediately.
Audit Trivy Versions
Check whether your organization pulled or executed Trivy v0.69.4 from any source. Remove any affected artifacts immediately.
Audit GitHub Action References
Review all workflows using aquasecurity/trivy-action or aquasecurity/setup-trivy. Check workflow run logs from March 19–20, 2026 for signs of compromise.
Search for Exfiltration Artifacts
Look for repositories named tpcp-docs in your 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 SHA Hashes
Pin GitHub Actions to full, immutable commit SHA hashes, don't use mutable version tags. As described here: https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions
How to Verify Existing Installations
Binary verification
##### Download binary and sigstore bundle
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz"
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json"##### Verify signature
$ cosign verify-blob \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--bundle trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json \
trivy_0.69.2_Linux-64bit.tar.gz
Verified OK
##### Check signing timestamp
$ date -u -d @$(jq -r '.verificationMaterial.tlogEntries[].integratedTime' trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json)
Sat Mar 1 19:11:02 UTC 2026
##### ✅ Signed on Mar 1, before the attack on Mar 19
Container image verification
##### Verify signature and get image digest
$ cosign verify \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--new-bundle-format \
ghcr.io/aquasecurity/trivy:0.69.2
Verification for ghcr.io/aquasecurity/trivy:0.69.2 --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The code-signing certificate was verified using trusted certificate authority certificates
##### Get digest and check all signing timestamps via Rekor
$ DIGEST=$(cosign verify \ --certificate-identity-regexp 'https://github\.com/aquasecurity/' \ --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \ --new-bundle-format -o json ghcr.io/aquasecurity/trivy:0.69.2 2>/dev/null | \ jq -r '.[0].critical.image."docker-manifest-digest"')
$ rekor-cli search --sha "$DIGEST"| grep -v 'Found'|whileread uuid;do
rekor-cli get --uuid "$uuid"| grep IntegratedTime
done
IntegratedTime: 2026-03-01T19:13:52Z
IntegratedTime: 2026-03-01T19:13:47Z
IntegratedTime: 2026-03-01T19:13:57Z
IntegratedTime: 2026-03-01T19:13:54Z
IntegratedTime: 2026-03-01T19:13:46Z
IntegratedTime: 2026-03-01T19:13:37Z
##### ✅ All signed on Mar 1, before the attack on Mar 19
Indicators of Compromise
Executable binaries
SHA256Filename
c5b16c42dbd2a1494141cd651a406ec9094d5031a421c0aa624c4d139ae81239trivy_0.69.4_FreeBSD_64bit.tar.gz
cff74e3e9ac0cda2078d31800d8fcad832d7b52c9920b085054d1e96dacff8a3trivy_0.69.4_Linux-32bit.deb
55047c55a5ceab6d80b13884b4a4e8cd27a0bab7a218a952a00aae9e05f16f80trivy_0.69.4_Linux-32bit.rpm
ba04ba6a0c028cde17599c8ddaefdb854055c5a23c595e06630732002ea59a76trivy_0.69.4_Linux-32bit.tar.gz
0ca60dd18178d1c79d59cc06be12c540c121a4aea467484244667131aa13c311trivy_0.69.4_Linux-64bit.deb
a5696321a6c93071f46c8bb8cbd0a8d2bce6d1860cc3c109247a4e8b64ebd317trivy_0.69.4_Linux-64bit.rpm
385d498d18a3a7c67878ca7322716f9da25683eb1a4bf9e9592da0d5f2ab09f6trivy_0.69.4_Linux-64bit.tar.gz
8f0c7b92b251c61cbca2add06c676dd21fde8fbb2d0cd6616383fae29b21756atrivy_0.69.4_Linux-ARM.deb
c5df9d1bc6275711b2884a9ed4aacfe4e10dbe3c8f6c79df59126fd0e6dcd83ftrivy_0.69.4_Linux-ARM.rpm
f7a9bbfec8add36c548add4d875848b8b57c21fabe236d115f1c49113d12b332trivy_0.69.4_Linux-ARM.tar.gz
9a833d68a49ec6d44bc50fb9ff3b184bafb0edc913e1293daebe51d334676a70trivy_0.69.4_Linux-ARM64.deb
451ce0c4deb620894d07a2f4a37c8ea3b7a4f9b6d111651b4ac3bcc737b0fac0trivy_0.69.4_Linux-ARM64.rpm
e401ae1e6d2442fa9a0c79dc0f3b0457ecfebf74a9c0a920159c49437f663aeftrivy_0.69.4_Linux-ARM64.tar.gz
284622577cf6a7c58704de60194205f765fcef432934c200b462ef0290aa5f57trivy_0.69.4_Linux-PPC64LE.deb
5fac89e66d70cadec5c0e30c0b0cf8bf38c145cbf06422d40d076985195e1dd6trivy_0.69.4_Linux-PPC64LE.rpm
52518d441fd6dd25fa5126683a330592d3be80d5ce3fb9e0b1becb806ff4f857trivy_0.69.4_Linux-PPC64LE.tar.gz
62585efcdc7767f3fe0b9ae2897fe03bf331934492fd7a5da46f14fd7bf705c8trivy_0.69.4_Linux-s390x.deb
107be2081bdc3ddad2889ae037ab2ad6bbd214fb9a43eaa25390d00411d1c7ddtrivy_0.69.4_Linux-s390x.rpm
16c855c398a8b185a907790054b70164358844a893bf9965651b88d6967c7c0atrivy_0.69.4_Linux-s390x.tar.gz
90d61cf37355b89fae9ff84867100e1721c1876007ef1771e465ce5a721141adtrivy_0.69.4_macOS-64bit.tar.gz
1dc871b02cd7a1fd80babb1b8762a2fd9cc2b735d4d3759d012626de3ccc7a5btrivy_0.69.4_macOS-ARM64.tar.gz
0376b98064636c30f5fbe60fb3b1225516e23e88dd7e909937f81d9265292e7dtrivy_0.69.4_windows_64bit.zip
822dd269ec10459572dfaaefe163dae693c344249a0161953f0d5cdd110bd2a0trivy_0.69.4_linux_amd64
e64e152afe2c722d750f10259626f357cdea40420c5eedae37969fbf13abbecftrivy_0.69.4_linux_arm64
d5edd791021b966fb6af0ace09319ace7b97d6642363ef27b3d5056ca654a94ctrivy_0.69.4_s390x
ecce7ae5ffc9f57bb70efd3ea136a2923f701334a8cd47d4fbf01a97fd22859ctrivy_0.69.4_ppc64le
Container images (v0.69.4)
DigestTag
sha256:27f446230c60bbf0b70e008db798bd4f33b7826f9f76f756606f5417100beef30.69.4
sha256:12c702212dee1cbec9471e9261501a3335963321fe76e60e5a715b5acd3c40a20.69.4-linux/amd64
sha256:2d7cee41048988eec27615412e7c6e2e21046f2b5faa888c24e11ca6764058ed0.69.4-linux/arm64
sha256:ae3494bd6ae860d7727116681bd09fc7b20dc994ec7a8105738f0a623ea934270.69.4-linux/ppc64le
sha256:43f46547efd488e56dcf862ed4d7cc342730a803f8d5bec5cac443028fefabef0.69.4- linux/s390x
sha256:cc464a3961e1dbe145c75343b55c2f446e08b821782ec993728c4222b0d855890.69.4-signature
sha256:5aaa1d7cfa9ca4649d6ffad165435c519dc836fa6e21b729a2174ad10b057d2b0.69.5
sha256:95ff680103570179feb0c6667a9b9b2d98c53fa5a9a451265036810390bbe70a0.69.5-linux/arm64
sha256:4f7a06bb51714713ab308d2f8125f3b09ee1c3ffbba1a5ffd0cc80da95fbb6cc0.69.5-linux/ppc64le
sha256:edef8e5816eced552a909b878ff262c0c47776d3297bcc23796ad4cce1e854140.69.5-linux/s390x
sha256:425cd3e1a2846ac73944e891250377d2b03653e6f028833e30fc00c1abbc6d330.69.6
sha256:dd8beb3b40df080b3fd7f9a0f5a1b02f3692f65c68980f46da8328ce8bb788ef0.69.6-linux/amd64
sha256:4b22cedea58780ff76735c3e08b9ee8cb5d06c908ffa868152f11d45349eb6960.69.6-linux/arm64
sha256:9efd59534d2b6b81b8b7a0eeb3ad0e74015f358650e24b9dab00c900d31185930.69.6-linux/ppc64le
sha256:5e5fb53cf4ce5555171ff5206302ba2f4f66f5381bbf673c354c87a925473f070.69.6-linux/s390x
Network
C2/sinks:
  • scan.aquasecurtiy.org
  • 45.148.10.212
GitHub Repositories
Public repo on victim's GitHub account with tpcp-docs- prefix.

Stolen data uploaded as a release asset with tag data-<timestamp>.
Severity
  • CVSS Score: 9.4 / 10 (Critical)
  • 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
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
aquasecurity/trivy-action (aquasecurity/trivy-action)
v0.35.0: Release: v0.35.0
Compare Source
This release is a duplicate of 0.35.0 which was not compromised.
As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.
We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.
If you are currently using 0.35.0, your workflows are safe — no action is required.
v0.35.0: Release: v0.35.0
Compare Source
This release is a duplicate of 0.35.0 which was not compromised.
As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.
We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.
If you are currently using 0.35.0, your workflows are safe — no action is required.
v0.34.0: Release: v0.34.0
Compare Source
Full Changelog: aquasecurity/trivy-action@v0.33.1...v0.34.0
Configuration
📅 Schedule: (UTC)
  • Branch creation

    • At any time (no schedule defined)
  • Automerge

    • At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
  •  If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Footnotes
  1. Time when v0.69.4 release artifacts became publicly available. The malicious tag was pushed at ~17:43 UTC, triggering the release pipeline. ↩
  2. Earliest suspicious activity observed in our audit log. ↩↩2
@renovaterenovateBot
added

package:github-actions
Pull requests that update action deps
type:dependencies
Pull requests that update a dependency file
update:minor
Minor Updates of dependency
labels
Mar 24, 2026
@snyk-io
snyk-ioBot
commented
Mar 24, 2026•

edited

Loading

Copy link


Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.
StatusScan Engine Critical High Medium LowTotal (0)
✅Open Source Security0000 0 issues
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMar 27, 2026
@renovaterenovateBot
closed this
Mar 27, 2026
@renovate
renovateBot
deleted the

renovate/github-tags-aquasecurity-trivy-action-vulnerability

branch
March 27, 2026 01:57
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Mar 28, 2026
@renovaterenovateBot
reopened this
Mar 28, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
24158b3 to
8c3ea0aCompareMarch 28, 2026 01:05
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedApr 4, 2026
@renovaterenovateBot
closed this
Apr 4, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Apr 4, 2026
@renovaterenovateBot
reopened this
Apr 4, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
8c3ea0a to
58cfc9aCompareApril 4, 2026 20:54
@renovaterenovateBot
added
the 
status:ready-to-merge
PR is ready to merge, skips approving
label
Apr 18, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMay 1, 2026
@renovaterenovateBot
closed this
May 1, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]May 2, 2026
@renovaterenovateBot
reopened this
May 2, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
58cfc9a to
bc5d01cCompareMay 2, 2026 01:42
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 10, 2026
@renovaterenovateBot
closed this
Jul 10, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 10, 2026
@renovaterenovateBot
reopened this
Jul 10, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
bc5d01c to
1b9d045CompareJuly 10, 2026 19:13
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 16, 2026
@renovaterenovateBot
closed this
Jul 16, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 16, 2026
@renovaterenovateBot
reopened this
Jul 16, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
1b9d045 to
06294b3CompareJuly 16, 2026 15:06
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedAug 24, 2026
@renovaterenovateBot
closed this
Aug 24, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Aug 25, 2026
@renovaterenovateBot
reopened this
Aug 25, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
from
06294b3 to
004fe91CompareAugust 25, 2026 20:12
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

package:github-actionsPull requests that update action depsstatus:ready-to-mergePR is ready to merge, skips approvingtype:dependenciesPull requests that update a dependency fileupdate:minorMinor Updates of dependency

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - #145
Open
renovate[bot] wants to merge 1 commit into
devfrom 
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Open
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]#145
renovate[bot] wants to merge 1 commit into
devfrom 
renovate/github-tags-aquasecurity-trivy-action-vulnerability
Conversation
@renovate
@renovaterenovateBot
commented
Mar 24, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
This PR contains the following updates:
PackageTypeUpdateChange
aquasecurity/trivy-actionactionminor0.33.1 → 0.35.0
Trivy Action has a script injection via sourced env file in composite action
CVE-2026-26189 / GHSA-9p44-j4g5-cfx5
More information
Details
Command Injection in aquasecurity/trivy-action via Unsanitized Environment Variable Export
A command injection vulnerability exists in aquasecurity/trivy-action due to improper handling of action inputs when exporting environment variables. The action writes export VAR=<input> lines to trivy_envs.txt based on user-supplied inputs and subsequently sources this file in entrypoint.sh.
Because input values are written without appropriate shell escaping, attacker-controlled input containing shell metacharacters (e.g., $(...), backticks, or other command substitution syntax) may be evaluated during the sourcing process. This can result in arbitrary command execution within the GitHub Actions runner context.
Severity:
Moderate
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
CWE-78: Improper Neutralization of Special Elements used in an OS Command (‘OS Command Injection’)
Impact:
Successful exploitation may lead to arbitrary command execution in the CI runner environment.
Affected Versions:
  • Versions >= 0.31.0 and <= 0.33.1
  • Introduced in commit 7aca5ac
Affected Conditions:
The vulnerability is exploitable when a consuming workflow passes attacker-controlled data into any action input that is written to trivy_envs.txt. Access to user input is required by the malicious actor.
A representative exploitation pattern involves incorporating untrusted pull request metadata into an action parameter. For example:
- uses: aquasecurity/trivy-action@0.33.1with:
output: "trivy-$.sarif"
If the pull request title contains shell syntax, it may be executed when the generated environment file is sourced.
Not Affected:
  • Workflows that do not pass attacker-controlled data into trivy-action inputs
  • Workflows that upgrade to a patched version that properly escapes shell values or eliminates the source ./trivy_envs.txt pattern
  • Workflows where user input is not accessible.
Call Sites:
  • action.yaml:188 — set_env_var_if_provided writes unescaped export lines
  • entrypoint.sh:9 — sources ./trivy_envs.txt
Severity
  • CVSS Score: 5.9 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Trivy ecosystem supply chain was briefly compromised
CVE-2026-33634 / GHSA-69fq-xp46-6x23
More information
Details
Summary
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.

On March 22, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.5 and v0.69.6 DockerHub images.
Exposure Window
ComponentStart (UTC)End (UTC)Duration
trivy v0.69.42026-03-19 18:22 12026-03-19 ~21:42~3 hours
trivy-action2026-03-19 ~17:43 22026-03-20 ~05:40~12 hours
setup-trivy2026-03-19 ~17:43 22026-03-19 ~21:44~4 hours
dockerhub trivy images v0.69.5 and v0.69.62026-03-22 15:432026-03-23 ~01:40~10 hours
Affected Components
Note that all malicious components, artifacts, commits, etc have been removed from all sources and destinations (yet they may linger in intermediary caches). Use this information to understand if you have been exposed to the malicious artifacts during the exposure window.
trivy binary and image
You are affected if you used:
  1. trivy binaries version v0.69.4 (or latest during the exposure window) distributed via GitHub, Deb, RPM.
  2. trivy container images v0.69.4 (or latest during the exposure window) distributed via GHCR, ECR public, Docker Hub.
  3. trivy container images v0.69.5 and v0.69.6 (or latest during the exposure window) distributed via Docker Hub.
You are not affected if you used:
  1. trivy (binary or image) version v0.69.3 or earlier.

    1. v0.69.3 is protected by GitHub's immutable releases feature (enabled March 3, before v0.69.3 was published).
    2. v0.69.2 predates immutable releases enablement but integrity can be verified via sigstore signatures (see "How to Verify" section below).
  2. trivy images referenced by digest.
  3. trivy binaries built from source.

    1. The malicious code was not committed to Trivy's main branch. It was fetched and built on the ephemeral runner, and also committed to a v0.70.0 branch but no release or git tag was ever pushed.
  4. homebrew from official formula (brew install trivy)

    1. The official homebrew formula is building trivy directly from source.
    2. There's an additional custom trivy tap which was compromised as part of the v0.69.4 release, but that tap requires special installation and is not even mentioned in the trivy documentation.
aquasecurity/trivy-action GitHub Action
You are affected if you used:
  1. Any tags prior except 0.35.0 (0.0.1 – 0.34.2) to reference the action.
  2. the action's version: latest parameter explicitly (not the default) during the trivy binary exposure window.
  3. SHA pinning to a commit prior to 2025-04-09.

    1. trivy-action started pinning setup-go with pull request trivy-action#456. If you pinned trivy-action to a commit prior to that PR (merged 2025-04-09), then you would get a safe trivy-action but it would get a malicious setup-trivy, if invoked during the setup-trivy exposure window.
You are not affected if you used:
  1. 0.35.0 tag

    1. 0.35.0 is protected by GitHub's immutable releases feature (enabled March 4, before 0.35.0 was published) and was not affected by the tag hijacking attack.
  2. SHA pinning to a safe commit commit after 2025-04-09.
aquasecurity/setup-trivy GitHub Action
You are affected if you used:
  1. Any version without pinning.
You are not affected if you used:
  1. SHA pinning to a safe commit.
Attack Details
Root Cause
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.
Trivy v0.69.4 binary and container images
The attacker created a malicious release by:
  1. Pushing a commit (1885610c) that swapped the actions/checkout reference to an imposter commit (70379aad) containing a composite action that downloaded malicious Go source files from a typosquatted domain
  2. Adding --skip=validate to goreleaser to bypass binary validation
  3. Tagging this commit as v0.69.4, triggering the release pipeline
The compromised release was distributed across Trivy's regular distribution channels channels: GHCR, ECR Public, Docker Hub (both 0.69.4 and latest tags), deb/rpm packages, and get.trivy.dev.
The attacker attempted to release a v0.70.0 malicious release but that was stopped prematurely.
trivy-action tag hijacking
The attacker force-pushed 76 of 77 version tags to malicious commits that injected an infostealer into entrypoint.sh. The malicious code executes before the legitimate Trivy scan and does the following:
  1. Dumps Runner.Worker process memory via /proc/<pid>/mem to extract secrets. Sweeps 50+ filesystem paths for SSH keys, AWS/GCP/Azure credentials, Kubernetes tokens, Docker configs, .env files, database credentials, and cryptocurrency wallets.
  2. Encrypts collected data using AES-256-CBC with RSA-4096 hybrid encryption.
  3. Transmits to attacker-controlled infrastructure. If exfiltration fails and INPUT_GITHUB_PAT is set, creates a public tpcp-docs repository on the victim's GitHub account and uploads stolen data as a release asset.
setup-trivy release replacement
All 7 existing tags (v0.2.0 – v0.2.6) were force-pushed to malicious commits. The malicious action.yaml contained the same infostealer as trivy-action, injected as a "Setup environment" step that executes before the legitimate Trivy installation.

We have removed all malicious releases within ~4 hours and re-created v0.2.6 with safe content. Tags v0.2.0 – v0.2.5 were not restored.
Trivy v0.69.5 and v0.69.6 docker image published.
The attacker created aquasec/trivy:0.69.5 and aquasec/trivy:0.69.6 with the same C2 domain as the v0.69.4 payload, and pushed them directly to Docker Hub using separately-compromised Docker Hub credentials (not via GitHub). No corresponding GitHub tags or releases existed.

We have removed all tags related to 0.69.5 and 0.69.6 and restored the latest tag to the safe 0.69.3 tag.
Recommended Actions
Update to Known-Safe Versions
ComponentSafe Version
Trivy binaryv0.69.2, v0.69.3
trivy-actionv0.35.0
setup-trivyv0.2.6
Regarding trivy-action: The original tags (0.0.1 – 0.34.2) were deleted during remediation. Because the attacker's force-push caused these tags to be treated as immutable releases by GitHub, they cannot be re-created with the same names. New tags have been published with a v prefix (v0.0.1 – v0.34.2) pointing to the original legitimate commits. Three tags: v0.0.10, v0.34.1, and v0.34.2 have not yet been restored. If you need to reference a version older than 0.35.0, use the v-prefixed tag (e.g., aquasecurity/trivy-action@v0.34.0 instead of @0.34.0).
Rotate All Potentially Exposed Secrets
Based on information shared above, if there is any possibility that a compromised version ran in your environment, all secrets accessible to affected pipelines must be treated as exposed and rotated immediately.
Audit Trivy Versions
Check whether your organization pulled or executed Trivy v0.69.4 from any source. Remove any affected artifacts immediately.
Audit GitHub Action References
Review all workflows using aquasecurity/trivy-action or aquasecurity/setup-trivy. Check workflow run logs from March 19–20, 2026 for signs of compromise.
Search for Exfiltration Artifacts
Look for repositories named tpcp-docs in your 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 SHA Hashes
Pin GitHub Actions to full, immutable commit SHA hashes, don't use mutable version tags. As described here: https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions
How to Verify Existing Installations
Binary verification
##### Download binary and sigstore bundle
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz"
curl -sLO "https://github.com/aquasecurity/trivy/releases/download/v0.69.2/trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json"##### Verify signature
$ cosign verify-blob \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--bundle trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json \
trivy_0.69.2_Linux-64bit.tar.gz
Verified OK
##### Check signing timestamp
$ date -u -d @$(jq -r '.verificationMaterial.tlogEntries[].integratedTime' trivy_0.69.2_Linux-64bit.tar.gz.sigstore.json)
Sat Mar 1 19:11:02 UTC 2026
##### ✅ Signed on Mar 1, before the attack on Mar 19
Container image verification
##### Verify signature and get image digest
$ cosign verify \
--certificate-identity-regexp 'https://github\.com/aquasecurity/' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--new-bundle-format \
ghcr.io/aquasecurity/trivy:0.69.2
Verification for ghcr.io/aquasecurity/trivy:0.69.2 --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The code-signing certificate was verified using trusted certificate authority certificates
##### Get digest and check all signing timestamps via Rekor
$ DIGEST=$(cosign verify \ --certificate-identity-regexp 'https://github\.com/aquasecurity/' \ --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \ --new-bundle-format -o json ghcr.io/aquasecurity/trivy:0.69.2 2>/dev/null | \ jq -r '.[0].critical.image."docker-manifest-digest"')
$ rekor-cli search --sha "$DIGEST"| grep -v 'Found'|whileread uuid;do
rekor-cli get --uuid "$uuid"| grep IntegratedTime
done
IntegratedTime: 2026-03-01T19:13:52Z
IntegratedTime: 2026-03-01T19:13:47Z
IntegratedTime: 2026-03-01T19:13:57Z
IntegratedTime: 2026-03-01T19:13:54Z
IntegratedTime: 2026-03-01T19:13:46Z
IntegratedTime: 2026-03-01T19:13:37Z
##### ✅ All signed on Mar 1, before the attack on Mar 19
Indicators of Compromise
Executable binaries
SHA256Filename
c5b16c42dbd2a1494141cd651a406ec9094d5031a421c0aa624c4d139ae81239trivy_0.69.4_FreeBSD_64bit.tar.gz
cff74e3e9ac0cda2078d31800d8fcad832d7b52c9920b085054d1e96dacff8a3trivy_0.69.4_Linux-32bit.deb
55047c55a5ceab6d80b13884b4a4e8cd27a0bab7a218a952a00aae9e05f16f80trivy_0.69.4_Linux-32bit.rpm
ba04ba6a0c028cde17599c8ddaefdb854055c5a23c595e06630732002ea59a76trivy_0.69.4_Linux-32bit.tar.gz
0ca60dd18178d1c79d59cc06be12c540c121a4aea467484244667131aa13c311trivy_0.69.4_Linux-64bit.deb
a5696321a6c93071f46c8bb8cbd0a8d2bce6d1860cc3c109247a4e8b64ebd317trivy_0.69.4_Linux-64bit.rpm
385d498d18a3a7c67878ca7322716f9da25683eb1a4bf9e9592da0d5f2ab09f6trivy_0.69.4_Linux-64bit.tar.gz
8f0c7b92b251c61cbca2add06c676dd21fde8fbb2d0cd6616383fae29b21756atrivy_0.69.4_Linux-ARM.deb
c5df9d1bc6275711b2884a9ed4aacfe4e10dbe3c8f6c79df59126fd0e6dcd83ftrivy_0.69.4_Linux-ARM.rpm
f7a9bbfec8add36c548add4d875848b8b57c21fabe236d115f1c49113d12b332trivy_0.69.4_Linux-ARM.tar.gz
9a833d68a49ec6d44bc50fb9ff3b184bafb0edc913e1293daebe51d334676a70trivy_0.69.4_Linux-ARM64.deb
451ce0c4deb620894d07a2f4a37c8ea3b7a4f9b6d111651b4ac3bcc737b0fac0trivy_0.69.4_Linux-ARM64.rpm
e401ae1e6d2442fa9a0c79dc0f3b0457ecfebf74a9c0a920159c49437f663aeftrivy_0.69.4_Linux-ARM64.tar.gz
284622577cf6a7c58704de60194205f765fcef432934c200b462ef0290aa5f57trivy_0.69.4_Linux-PPC64LE.deb
5fac89e66d70cadec5c0e30c0b0cf8bf38c145cbf06422d40d076985195e1dd6trivy_0.69.4_Linux-PPC64LE.rpm
52518d441fd6dd25fa5126683a330592d3be80d5ce3fb9e0b1becb806ff4f857trivy_0.69.4_Linux-PPC64LE.tar.gz
62585efcdc7767f3fe0b9ae2897fe03bf331934492fd7a5da46f14fd7bf705c8trivy_0.69.4_Linux-s390x.deb
107be2081bdc3ddad2889ae037ab2ad6bbd214fb9a43eaa25390d00411d1c7ddtrivy_0.69.4_Linux-s390x.rpm
16c855c398a8b185a907790054b70164358844a893bf9965651b88d6967c7c0atrivy_0.69.4_Linux-s390x.tar.gz
90d61cf37355b89fae9ff84867100e1721c1876007ef1771e465ce5a721141adtrivy_0.69.4_macOS-64bit.tar.gz
1dc871b02cd7a1fd80babb1b8762a2fd9cc2b735d4d3759d012626de3ccc7a5btrivy_0.69.4_macOS-ARM64.tar.gz
0376b98064636c30f5fbe60fb3b1225516e23e88dd7e909937f81d9265292e7dtrivy_0.69.4_windows_64bit.zip
822dd269ec10459572dfaaefe163dae693c344249a0161953f0d5cdd110bd2a0trivy_0.69.4_linux_amd64
e64e152afe2c722d750f10259626f357cdea40420c5eedae37969fbf13abbecftrivy_0.69.4_linux_arm64
d5edd791021b966fb6af0ace09319ace7b97d6642363ef27b3d5056ca654a94ctrivy_0.69.4_s390x
ecce7ae5ffc9f57bb70efd3ea136a2923f701334a8cd47d4fbf01a97fd22859ctrivy_0.69.4_ppc64le
Container images (v0.69.4)
DigestTag
sha256:27f446230c60bbf0b70e008db798bd4f33b7826f9f76f756606f5417100beef30.69.4
sha256:12c702212dee1cbec9471e9261501a3335963321fe76e60e5a715b5acd3c40a20.69.4-linux/amd64
sha256:2d7cee41048988eec27615412e7c6e2e21046f2b5faa888c24e11ca6764058ed0.69.4-linux/arm64
sha256:ae3494bd6ae860d7727116681bd09fc7b20dc994ec7a8105738f0a623ea934270.69.4-linux/ppc64le
sha256:43f46547efd488e56dcf862ed4d7cc342730a803f8d5bec5cac443028fefabef0.69.4- linux/s390x
sha256:cc464a3961e1dbe145c75343b55c2f446e08b821782ec993728c4222b0d855890.69.4-signature
sha256:5aaa1d7cfa9ca4649d6ffad165435c519dc836fa6e21b729a2174ad10b057d2b0.69.5
sha256:95ff680103570179feb0c6667a9b9b2d98c53fa5a9a451265036810390bbe70a0.69.5-linux/arm64
sha256:4f7a06bb51714713ab308d2f8125f3b09ee1c3ffbba1a5ffd0cc80da95fbb6cc0.69.5-linux/ppc64le
sha256:edef8e5816eced552a909b878ff262c0c47776d3297bcc23796ad4cce1e854140.69.5-linux/s390x
sha256:425cd3e1a2846ac73944e891250377d2b03653e6f028833e30fc00c1abbc6d330.69.6
sha256:dd8beb3b40df080b3fd7f9a0f5a1b02f3692f65c68980f46da8328ce8bb788ef0.69.6-linux/amd64
sha256:4b22cedea58780ff76735c3e08b9ee8cb5d06c908ffa868152f11d45349eb6960.69.6-linux/arm64
sha256:9efd59534d2b6b81b8b7a0eeb3ad0e74015f358650e24b9dab00c900d31185930.69.6-linux/ppc64le
sha256:5e5fb53cf4ce5555171ff5206302ba2f4f66f5381bbf673c354c87a925473f070.69.6-linux/s390x
Network
C2/sinks:
  • scan.aquasecurtiy.org
  • 45.148.10.212
GitHub Repositories
Public repo on victim's GitHub account with tpcp-docs- prefix.

Stolen data uploaded as a release asset with tag data-<timestamp>.
Severity
  • CVSS Score: 9.4 / 10 (Critical)
  • 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
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
aquasecurity/trivy-action (aquasecurity/trivy-action)
v0.35.0: Release: v0.35.0
Compare Source
This release is a duplicate of 0.35.0 which was not compromised.
As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.
We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.
If you are currently using 0.35.0, your workflows are safe — no action is required.
v0.35.0: Release: v0.35.0
Compare Source
This release is a duplicate of 0.35.0 which was not compromised.
As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.
We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.
If you are currently using 0.35.0, your workflows are safe — no action is required.
v0.34.0: Release: v0.34.0
Compare Source
Full Changelog: aquasecurity/trivy-action@v0.33.1...v0.34.0
Configuration
📅 Schedule: (UTC)
  • Branch creation

    • At any time (no schedule defined)
  • Automerge

    • At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
  •  If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Footnotes
  1. Time when v0.69.4 release artifacts became publicly available. The malicious tag was pushed at ~17:43 UTC, triggering the release pipeline. ↩
  2. Earliest suspicious activity observed in our audit log. ↩↩2
@renovaterenovateBot
added

package:github-actions
Pull requests that update action deps
type:dependencies
Pull requests that update a dependency file
update:minor
Minor Updates of dependency
labels
Mar 24, 2026
@snyk-io
snyk-ioBot
commented
Mar 24, 2026•

edited

Loading

Copy link


Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.
StatusScan Engine Critical High Medium LowTotal (0)
✅Open Source Security0000 0 issues
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMar 27, 2026
@renovaterenovateBot
closed this
Mar 27, 2026
@renovate
renovateBot
deleted the

renovate/github-tags-aquasecurity-trivy-action-vulnerability

branch
March 27, 2026 01:57
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Mar 28, 2026
@renovaterenovateBot
reopened this
Mar 28, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
24158b3 to
8c3ea0aCompareMarch 28, 2026 01:05
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedApr 4, 2026
@renovaterenovateBot
closed this
Apr 4, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Apr 4, 2026
@renovaterenovateBot
reopened this
Apr 4, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
8c3ea0a to
58cfc9aCompareApril 4, 2026 20:54
@renovaterenovateBot
added
the 
status:ready-to-merge
PR is ready to merge, skips approving
label
Apr 18, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedMay 1, 2026
@renovaterenovateBot
closed this
May 1, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]May 2, 2026
@renovaterenovateBot
reopened this
May 2, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
58cfc9a to
bc5d01cCompareMay 2, 2026 01:42
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 10, 2026
@renovaterenovateBot
closed this
Jul 10, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 10, 2026
@renovaterenovateBot
reopened this
Jul 10, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
bc5d01c to
1b9d045CompareJuly 10, 2026 19:13
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedJul 16, 2026
@renovaterenovateBot
closed this
Jul 16, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Jul 16, 2026
@renovaterenovateBot
reopened this
Jul 16, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
2 times, most recently
from
1b9d045 to
06294b3CompareJuly 16, 2026 15:06
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedAug 24, 2026
@renovaterenovateBot
closed this
Aug 24, 2026
@renovaterenovateBot
changed the title
chore(deps): update aquasecurity/trivy-action action to v0.35.0 [security] - autoclosedchore(deps): update aquasecurity/trivy-action action to v0.35.0 [security]Aug 25, 2026
@renovaterenovateBot
reopened this
Aug 25, 2026
@renovate
renovateBotforce-pushed
the
renovate/github-tags-aquasecurity-trivy-action-vulnerability
branch
from
06294b3 to
004fe91CompareAugust 25, 2026 20:12
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

package:github-actionsPull requests that update action depsstatus:ready-to-mergePR is ready to merge, skips approvingtype:dependenciesPull requests that update a dependency fileupdate:minorMinor Updates of dependency

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants