CVE-2026-63328: Github.com/aquasecurity/trivy Path Traversal Vulnerability

MODERATE
Advisory Identifier: GHSA-8rc5-4fr6-64pw
CWE-22
Published
Advisory Summary

CVE-2026-63328 is a MODERATE path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Github.com/aquasecurity/trivy libraries in the Go ecosystem. The issue involves trivy plugin manager has path traversal that allows arbitrary file write. Remediation is available by upgrading affected packages to version 0.72.0.

CVE-2026-63328 at a Glance

CVE Identifier CVE-2026-63328
GHSA Identifier GHSA-8rc5-4fr6-64pw
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Github.com/aquasecurity/trivy
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-63328

To remediate this vulnerability, upgrade all affected Github.com/aquasecurity/trivy dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/aquasecurity/trivy fixed: 0.72.0
Upgrade github.com/aquasecurity/trivy to 0.72.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/aquasecurity/trivy

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-63328, inspect your project dependencies for Github.com/aquasecurity/trivy:

inspect dependencies for github.com/aquasecurity/trivy

Analyze the terminal output to locate any version of Github.com/aquasecurity/trivy in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.72.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Github.com/aquasecurity/trivy, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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](https://trivy.dev/docs/latest/guide/plugin/) 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>` or `trivy 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](https://trivy.dev/docs/latest/guide/plugin/) for details. ## Credits Reported by @fatihhcelik.

CVE-2026-63328 Affected Github.com/aquasecurity/trivy Versions

1 component(s)
Fixed Versions:
0.72.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/aquasecurity/trivy
Go
< 0.72.0
0.72.0

References

Frequently Asked Questions

What is CVE-2026-63328?
CVE-2026-63328 is a security vulnerability in Github.com/aquasecurity/trivy involving Trivy Plugin Manager has Path Traversal that Allows Arbitrary File Write under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Github.com/aquasecurity/trivy versions are affected?
Affected versions include releases prior to 0.72.0 across affected packages: github.com/aquasecurity/trivy.
What version fixes CVE-2026-63328?
Upgrading to 0.72.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/aquasecurity/trivy affected?
Yes, github.com/aquasecurity/trivy is affected in releases prior to 0.72.0. Upgrade your dependency to 0.72.0 or later.
What CWE is associated with CVE-2026-63328?
CVE-2026-63328 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check Go dependencies for CVE-2026-63328?
Run the dependency tree command: 'inspect dependencies for github.com/aquasecurity/trivy'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8rc5-4fr6-64pw",
  "modified" : "2026-08-18T16:32:02Z",
  "published" : "2026-08-18T16:32:02Z",
  "aliases" : [ "CVE-2026-63328" ],
  "summary" : "Trivy Plugin Manager has Path Traversal that Allows Arbitrary File Write",
  "details" : "## Summary\n\nTrivy'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.\n\nPlugins are third-party binaries that Trivy downloads and executes, so Trivy's [documentation](https://trivy.dev/docs/latest/guide/plugin/) 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.\n\n## Affected configurations\n\nThe vulnerability is triggered only when a user installs an attacker-controlled plugin, for example via `trivy plugin install <SOURCE>` or `trivy 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.\n\nPlugins distributed through the official Trivy plugin index are not affected.\n\n## Impact\n\nA 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.\n\n## Patches\n\nFixed in Trivy `0.72.0`. Users should upgrade to that release or later.\n\n## Workarounds\n\nOnly install Trivy plugins from sources you trust. Plugins from the official Trivy plugin index are safe. See the [plugin documentation](https://trivy.dev/docs/latest/guide/plugin/) for details.\n\n## Credits\n\nReported by @fatihhcelik.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/aquasecurity/trivy"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.72.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/aquasecurity/trivy/security/advisories/GHSA-8rc5-4fr6-64pw"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/aquasecurity/trivy/commit/d4213d7735c74e57f06c02ccb39ebca67abc7959"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/aquasecurity/trivy"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/aquasecurity/trivy/releases/tag/v0.72.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-18T16:32:02Z",
    "nvd_published_at" : null
  }
}