CVE-2026-104994: Low severity Aqua Security Trivy vulnerability
Trivy before 0.71.0 allows directory traversal in Terraform filesystem functions when they try to access pathnames above the scan root. The risk occurs when using misconf scanning on untrusted input (e.g., upon a third-party pull request that contains a Terraform configuration), if sensitive data can be found at those unintended pathnames, and an adversary can then view a sensitive data value within scan output.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Trivyto a version that resolves this vulnerability.Fixed in 0.71.0
Event History
Frequently Asked Questions
Who is realistically exposed to this issue?
Teams using Trivy misconfiguration scanning on untrusted Terraform input are exposed, particularly CI workflows that scan configurations submitted in third-party pull requests. Exposure also requires sensitive data to be present at filesystem locations above the configured scan root.
What must an attacker be able to do to exploit it?
An attacker needs to provide a Terraform configuration that causes Terraform filesystem functions to access pathnames above the scan root. They must also be able to view scan output containing a sensitive value read from an unintended location.
Is this a concern for every Trivy scan?
No. The described risk is specific to misconfiguration scanning of Terraform input and depends on filesystem-function access outside the scan root. The issue affects Trivy versions before 0.71.0.