Repository navigation
Update module github.com/aquasecurity/trivy to v0.72.0 [SECURITY] - #576
Open
renovate-update-app[bot] wants to merge 1 commit into
Open
renovate-update-app[bot] wants to merge 1 commit into
renovate-update-app[bot] wants to merge 1 commit into
Conversation
![renovatee-approver-stackvista[bot]](https://avatars.githubusercontent.com/u/10511829?s=60&v=4){kind=small}
renovate-update-app
Bot
force-pushed
the
renovate/go-github.com-aquasecurity-trivy-vulnerability
branch
2 times, most recently
from
October 25, 2026 08:37
92b3ed7 to
7e81d80
Compare
renovate-update-app
Bot
force-pushed
the
renovate/go-github.com-aquasecurity-trivy-vulnerability
branch
from
October 26, 2026 08:45
7e81d80 to
7e333ca
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.63.0→v0.72.0Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Trivy: Helm chart tar bomb causes OOM via unbounded io.ReadAll in parser
CVE-2026-54448 / GHSA-q3fv-x8vg-qqm4 / GO-2026-5983
More information
Details
Summary
When Trivy scans a Helm chart archive (
.tgz), its custom tar unpacker reads each entry withio.ReadAll(tr)and no size limit. An attacker who can place a malicious.tgzfile in the scanned path can craft a small compressed archive that decompresses to gigabytes, causing the Trivy process to be killed by the OS OOM killer.Affected configurations
Exploitation requires the attacker to place a crafted
.tgzfile in a location that Trivy will scan as a Helm chart. This applies to the following scan targets:trivy config <dir>.tgzHelm chart (misconfiguration scanning is always enabled)trivy filesystem --scanners misconf <dir>.tgzHelm chart and--scanners misconfis explicitly enabledtrivy image --scanners misconf <image>.tgzHelm chart and--scanners misconfis explicitly enabledRealistic scenarios include:
trivy config .on a repository where a contributor can submit a pull request containing a crafted chart archive.--scanners misconf, whose build context includes untrusted.tgzfiles.Impact
An attacker who satisfies the conditions above can exhaust all available memory on the host running Trivy. The OS OOM killer will terminate the Trivy process and may affect other processes sharing the same host or CI runner.
The practical impact in CI environments is denial of service: the scan fails, the pipeline is blocked, and repeated submissions re-trigger the same condition. Cloud CI runners may also incur additional costs for consumed resources.
There is no impact on confidentiality or integrity of the scanned system.
Patches
Fixed in Trivy
v0.71.0(#10718). The custom tar unpacker was replaced witharchive.LoadArchiveFilesfrom the officialhelm.sh/helm/v4SDK, which enforces per-entry and total size limits and validates archive structure. Users should upgrade tov0.71.0or later.Workarounds
If upgrading is not immediately possible:
--skip-dirsto exclude directories containing untrusted Helm chart archives from the scan..tgzfiles.Credits
Reported by @jamesgol.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Trivy: Helm chart tar bomb causes OOM via unbounded io.ReadAll in parser in github.com/aquasecurity/trivy
CVE-2026-54448 / GHSA-q3fv-x8vg-qqm4 / GO-2026-5983
More information
Details
Trivy: Helm chart tar bomb causes OOM via unbounded io.ReadAll in parser in github.com/aquasecurity/trivy
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Trivy has a path traversal via a crafted vulnerability database or other downloaded artifacts
CVE-2026-55092 / GHSA-mcj4-mphf-j9ff / GO-2026-6294
More information
Details
Summary
When Trivy downloads an OCI artifact, it uses the
org.opencontainers.image.titleannotation from the artifact manifest as the destination filename without validation. An attacker who can make Trivy fetch an attacker-controlled artifact can supply a crafted annotation that resolves to a path outside the intended destination, causing Trivy to write the layer content to an arbitrary location on the host filesystem.Affected configurations
Exploitation requires the attacker to direct Trivy at an attacker-controlled OCI artifact via one of the following inputs:
--db-repositoryflag,TRIVY_DB_REPOSITORYenvironment variable, ordb.repositoryintrivy.yaml--java-db-repositoryflag,TRIVY_JAVA_DB_REPOSITORYenvironment variable, ordb.java-repositoryintrivy.yaml--checks-bundle-repositoryflag (and the deprecated--policy-bundle-repositoryalias),TRIVY_CHECKS_BUNDLE_REPOSITORYenvironment variable, ormisconfiguration.checks-bundle-repositoryintrivy.yamltrivy module install <REPO>Realistic scenarios in which an attacker may influence these inputs include a copy-pasted command or documentation snippet pointing to an untrusted mirror, or a third-party mirror that turns out to be hostile.
Trivy's default configuration, which downloads these artifacts from Aqua-operated repositories, is not affected. The risk applies only when one of the inputs above is overridden to download a different artifact.
Impact
An attacker who satisfies the conditions above can overwrite or create arbitrary files on the host filesystem within the privilege boundary of the user running Trivy. The vulnerability does not grant any privileges beyond what that user already has.
The practical impact depends on the deployment. In environments where the running user can overwrite files such as SSH
authorized_keys, shell startup files, cron entries, or binaries onPATH, the file write may be leveraged to achieve code execution as that user. In more restricted deployments, the impact is bounded to the user's writable scope but may still allow tampering with scan results, build artifacts, or other files consumed by subsequent steps in the same pipeline.Patches
Fixed in Trivy
0.71.1. Users should upgrade to that release or later.Workarounds
If upgrading is not immediately possible, do not download Trivy artifacts (vulnerability database, Java database, misconfiguration checks bundle, modules, etc.) from OCI repositories you do not operate or trust.
Credits
Reported by @ikkebr.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Path traversal via crafted vulnerability database or other downloaded artifacts in github.com/aquasecurity/trivy
CVE-2026-55092 / GHSA-mcj4-mphf-j9ff / GO-2026-6294
More information
Details
Path traversal via crafted vulnerability database or other downloaded artifacts in github.com/aquasecurity/trivy
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Trivy Plugin Manager has Path Traversal that Allows Arbitrary File Write
CVE-2026-63328 / GHSA-8rc5-4fr6-64pw / GO-2026-6250
More information
Details
Summary
Trivy's plugin manager does not fully validate metadata from a plugin's manifest before using it to construct filesystem paths under the plugin root (
~/.trivy/plugins). A crafted plugin can cause Trivy to write its files (the manifest and the downloaded plugin binary) outside the plugin root, to an arbitrary location writable by the user running Trivy.Plugins are third-party binaries that Trivy downloads and executes, so Trivy's documentation already advises installing only plugins you trust. This issue does not change that trust boundary: exploitation requires the user to install a malicious plugin in the first place.
Affected configurations
The vulnerability is triggered only when a user installs an attacker-controlled plugin, for example via
trivy plugin install <SOURCE>ortrivy plugin run <SOURCE>. An attacker has to trick a user into installing a plugin they crafted, for instance by publishing it or by getting a malicious source pasted into a command or documentation snippet.Plugins distributed through the official Trivy plugin index are not affected.
Impact
A user who installs a malicious plugin can have files written outside the plugin root, to any location writable by the user running Trivy. The vulnerability does not grant any privileges beyond what that user already has.
Patches
Fixed in Trivy
0.72.0. Users should upgrade to that release or later.Workarounds
Only install Trivy plugins from sources you trust. Plugins from the official Trivy plugin index are safe. See the plugin documentation for details.
Credits
Reported by @fatihhcelik.
Severity
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Trivy Plugin Manager has Path Traversal that Allows Arbitrary File Write in github.com/aquasecurity/trivy
CVE-2026-63328 / GHSA-8rc5-4fr6-64pw / GO-2026-6250
More information
Details
Trivy Plugin Manager has Path Traversal that Allows Arbitrary File Write in github.com/aquasecurity/trivy
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.