NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹 Go
Not in CISA KEV

Trivy Plugin Manager has Path Traversal that Allows Arbitrary File WriteGHSA-8rc5-4fr6-64pw

Fix: aquasecurity/trivy@d4213d7

GHSA-8rc5-4fr6-64pw is a Path Traversal vulnerability in github.com/aquasecurity/trivy. A fix is available for github.com/aquasecurity/trivy — see the affected versions and patch details below.

Also known asCVE-2026-63328GO-2026-6250
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 16, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-8rc5-4fr6-64pw.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs9th percentile — riskier than 9% of all scored CVEsHighest risk
0.00%0.23%0.46%0.69%0.2%0.2%0.2%0.2%Sep 26Nov 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected
🐹github.com/aquasecurity/trivy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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> 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 for details.

Credits

Reported by @fatihhcelik.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/aquasecurity/trivyall versions0.72.0go get github.com/aquasecurity/trivy@v0.72.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/aquasecurity/trivy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/aquasecurity/trivy to 0.72.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8rc5-4fr6-64pw is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This vulnerability is rated as Moderate impact because successful exploitation requires active user interaction to install an untrusted third-party plugin, and file write actions remain limited to the operating system permissions of the executing user account. Standard CLI scanning operations do not require or…

Workaround published by Red Hat
Avoid installing or executing Trivy plugins from untrusted sources. Limit plugin usage to verified plugins from the official Trivy plugin index, or refrain from using third-party plugins in automated scanning pipelines. Running scans within an isolated container with read-only filesystem mounts prevents unauthorized file creation outside expected directories.
Source: Red Hat security advisory for GHSA-8rc5-4fr6-64pw (CC BY 4.0)

Frequently Asked Questions

## 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 b
O3 Security · Impact-Aware SCA

Is GHSA-8rc5-4fr6-64pw in your dependencies?

Find it across Go, including transitive dependencies.

Trivy Plugin Manager has Path Traversal that Allows…