CVE-2026-63328 aquasecurity CVE debrief

Who should care

Defenders responsible for Trivy installations, especially those who install plugins from untrusted sources, should assess exposure and prioritize verification and remediation. They should verify Trivy installations, update to version 0.72.0 or later, and restrict plugin installations to trusted sources. Additionally, they should monitor Trivy installations for suspicious plugin activity and review compensating controls for exposed systems.

Why it matters

CVE-2026-63328 is a medium-severity vulnerability in Trivy that allows an attacker to write plugin data to arbitrary user-writable paths. Defenders should prioritize verifying Trivy installations, especially for users who install plugins from untrusted sources, and update to version 0.72.0 or later.

• Defenders must verify Trivy installations to prevent arbitrary file writes.
• Users who install plugins from untrusted sources are at higher risk of exposure.
• Remediation priority is high for systems with untrusted plugin sources.
• Additional monitoring may be required to detect suspicious plugin activity.

Technical summary

CVE-2026-63328 is a medium-severity vulnerability in Trivy, a security scanner. Prior to version 0.72.0, the plugin manifest metadata is used to construct paths under ~/.trivy/plugins without confining plugin names to that root. This allows an attacker who persuades a user to install or run a malicious plugin to write the manifest and plugin binary to arbitrary user-writable paths. The vulnerability is fixed in version 0.72.0. Defenders should prioritize verifying Trivy installations and assessing exposure, especially for users who install plugins from untrusted sources.

Defensive priority

Defenders should prioritize verifying Trivy installations and assessing exposure, especially for users who install plugins from untrusted sources.

Recommended defensive actions

• Verify Trivy installations and assess exposure, especially for users who install plugins from untrusted sources.
• Update Trivy to version 0.72.0 or later.
• Restrict plugin installations to trusted sources.
• Monitor Trivy installations for suspicious plugin activity.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impact, and the fixed version. However, additional information on potential exploitation or affected systems is limited. Defenders should verify Trivy installations, especially for users who install plugins from untrusted sources, and update to version 0.72.0 or later. The vulnerability is a result of the plugin manifest metadata being used to construct paths under ~/.trivy/plugins without confining plugin names to that root.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.