GHSA-8rc5-4fr6-64pw: Path Traversal

Published Aug 18, 2026
·
Updated

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 Software

1 affected componentFixes available
go/github.com/aquasecurity/trivy<0.72.0
0.72.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/aquasecurity/trivy to a version that resolves this vulnerability.

    Fixed in 0.72.0
  2. Upgrade

    Upgrade Trivy to a version that resolves this vulnerability.

    Fixed in 0.72.0
  3. Compensating control

    Only install Trivy plugins from sources you trust (plugins distributed through the official Trivy plugin index are not affected/safe).

Event History

Aug 18, 2026
Advisory Published
via GitHub·04:32 PM
Data Sourced
via GitHub·04:32 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What must an attacker do to exploit this issue?

Exposure requires a user to install or run an attacker-controlled plugin source, such as through "trivy plugin install <SOURCE>" or "trivy plugin run <SOURCE>". An attacker must persuade the user to use a crafted plugin, for example through a published plugin or a malicious command or documentation snippet.

2

Are users of plugins from the official plugin index exposed?

Plugins distributed through the official Trivy plugin index are not affected. The vulnerable path is installation of a malicious third-party plugin outside that official distribution channel.

3

What can be done until an update is applied?

Avoid installing or running untrusted plugin sources. Since exploitation requires installation of a malicious plugin, restricting plugin installation to trusted sources prevents this condition when patching cannot be performed immediately.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203