Is CVE-2026-63328 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63328 being exploited in the wild.

How severe is CVE-2026-63328?

Medium severity, with a CVSS score of 4, published 18 August 2026.

Which products and versions are affected?

Aqua Security Trivy < 0.72.0; github.com/aquasecurity/trivy (Go) < 0.72.0, SEMVER:introduced=0,fixed=0.72.0.

Is there a fix for CVE-2026-63328?

Yes. github.com/aquasecurity/trivy (Go): upgrade to 0.72.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-63328 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-63328?

Check whether you run Aqua Security Trivy or github.com/aquasecurity/trivy (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63328: Aqua Trivy plugin manager path traversal arbitrary file write

Q: Which products and versions are affected?

Aqua Security Trivy < 0.72.0; github.com/aquasecurity/trivy (Go) < 0.72.0, SEMVER:introduced=0,fixed=0.72.0.

Q: Is there a fix for CVE-2026-63328?

Yes. github.com/aquasecurity/trivy (Go): upgrade to 0.72.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-63328 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-63328?

Check whether you run Aqua Security Trivy or github.com/aquasecurity/trivy (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63328 · Severity: medium · CVSS 4 · Published 2026-08-18

Trivy is a vulnerability scanner that supports third-party plugins. The plugin manager fails to validate plugin metadata, allowing a malicious plugin to write files to any location on the system that the user running Trivy can access. An attacker must trick a user into installing the malicious plugin first. This could result in unauthorized modification of system files or data, but does not escalate the attacker's privileges beyond what the installing user already has.

Technologies: Aqua Security Trivy, github.com/aquasecurity/trivy (Go). Vendors: Aqua Security, Go.

Quick answers

Is CVE-2026-63328 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63328 being exploited in the wild.
How severe is CVE-2026-63328?: Medium severity, with a CVSS score of 4, published 18 August 2026.
Which products and versions are affected?: Aqua Security Trivy < 0.72.0; github.com/aquasecurity/trivy (Go) < 0.72.0, SEMVER:introduced=0,fixed=0.72.0.
Is there a fix for CVE-2026-63328?: Yes. github.com/aquasecurity/trivy (Go): upgrade to 0.72.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63328 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-63328?: Check whether you run Aqua Security Trivy or github.com/aquasecurity/trivy (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/aquasecurity/trivy (Go): upgrade to 0.72.0 or later
```
go get github.com/aquasecurity/trivy@v0.72.0
```

Technical details

The vulnerability is a path traversal flaw (CWE-22) in Trivy's plugin installation mechanism. The plugin manager constructs filesystem paths under the plugin root (~/.trivy/plugins) using unsanitized metadata from a plugin's manifest file. By crafting a manifest with path traversal sequences (e.g., using ../ components), an attacker can cause Trivy to write the plugin binary and manifest files outside the intended plugin directory. The attack requires user interaction—the user must install the malicious plugin via `trivy plugin install <SOURCE>` or `trivy plugin run <SOURCE>`—but does not require elevated privileges. Plugins from the official Trivy plugin index are unaffected. The vulnerability was patched in version 0.72.0.

Affected products

Aqua Security Trivy < 0.72.0

Identifiers

CVE-2026-63328
GHSA-8rc5-4fr6-64pw
GO-2026-6250

Timeline

2026-06-30: disclosed: Published to GitHub Advisory Database
2026-07-30: patched: Fixed in Trivy 0.72.0
2026-08-18: advisory: GitHub Advisory GHSA-8rc5-4fr6-64pw published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.