Skip to content
Fencer Vulns
low 2.5

CVE-2026-104994 json

Trivy before 0.71.0 allows directory traversal in Terraform filesystem functions when they try to access pathnames above the scan root.

published 2026-10-02 37 d ago modified 2026-10-05 34 d ago also EUVD-2026-91789

cvss
2.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits
0
none known

Summary

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.

Patch / fix

  • aquasec Trivy 0.71.0
  • trivy hummingbird 1 0.74.0-0.4.hum1

red hat advisories RHSA-2026:72492

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-104994 updated cvss 2.5

github.com/aquasecurity/trivy: Trivy: Information disclosure via directory traversal in Terraform filesystem functions

  • Red Hat Hardened Images trivy 0.74.0-0.4.hum1
    fixed: vendor fix RHSA-2026:72492

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
34 d ago

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 2.5 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected products

  • aquasec Trivy

Classification

Weakness
  • CWE-24 Path Traversal: '../filedir'

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.