# CVE-2026-104994: Path traversal in Trivy

> Attackers can read sensitive files outside the scan root via directory traversal in Terraform scanning, affecting developers using Trivy on untrusted inputs.

- **Severity:** Low 2.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-87hp-4m93-274g, GHSA-fr63-55g9-p68v

## What is CVE-2026-104994?

CVE-2026-104994 is a low-severity path traversal vulnerability in aquasec Trivy, published on 2 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-24 (Path Traversal: '../filedir')

## Which versions are affected by CVE-2026-104994?


## How do I fix CVE-2026-104994?

Upgrade to a fixed version.

## Is CVE-2026-104994 being exploited?

There is no known exploitation of CVE-2026-104994 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104994 and fix it if it is affected.

What it is: CVE-2026-104994 is a low-severity path traversal vulnerability in aquasec Trivy, published on 2 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-104994 in the wild and no public exploit code.

Affected product: aquasec Trivy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104994/ (Markdown: https://insights.sbomify.com/CVE-2026-104994/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104994
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104994
- OSV: https://osv.dev/vulnerability/CVE-2026-104994

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104994/
Summaries are generated and may contain mistakes; the official description above is the record.