# CVE-2026-55092: Trivy: Path traversal via a crafted vulnerability database or other downloaded artifacts

> An attacker can force Trivy to write files to arbitrary locations on the host filesystem by crafting a malicious OCI artifact annotation.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-mcj4-mphf-j9ff, GO-2026-6294, MINI-46gf-4h67-9q7v, MINI-48q6-3gv2-h459, MINI-52j7-25r3-v4m8, MINI-57mh-q5qm-5mvx, MINI-5r54-v82p-v9q5, MINI-5rh4-8gwg-q5qj, MINI-67cm-vpwj-f4qf, MINI-7pm3-79qv-wvfx, MINI-7rjw-rhrp-922r, MINI-8c38-53r5-69wc, MINI-8f4g-9gqg-j2fj, MINI-9hfr-fm35-4xf5, MINI-9xv9-56fh-pcvv, MINI-c4fg-gm5w-mcx3, MINI-c8gr-3v3r-grj9, MINI-cqx3-28jj-24pf, MINI-cwjf-j5wq-ccvj, MINI-fgpp-h8pj-gmvw, MINI-h5vj-3jmr-h9mm, MINI-j4r6-fpq5-g6r9, MINI-pxmp-7x86-v82m, MINI-q74v-rcrx-wvwv, MINI-qr37-w57w-4646, MINI-r3h2-96qq-7q4v, MINI-r756-fjpw-hf3v, MINI-w65q-ppp7-9f35, MINI-x4vv-9q8v-x5pm

## What is CVE-2026-55092?

CVE-2026-55092 is a high-severity path traversal vulnerability in aquasecurity trivy, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Trivy is a security scanner. Prior to 0.71.1, when Trivy downloads an OCI artifact, it uses the org.opencontainers.image.title annotation from the artifact manifest as the destination filename without validation. An attacker who can make Trivy fetch an attacker-controlled artifact can supply a crafted annotation that resolves to a path outside the intended destination, causing Trivy to write the layer content to an arbitrary location on the host filesystem. This vulnerability is fixed in 0.71.1.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

3 open source packages ship an affected version, including github.com/aquasecurity/trivy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/aquasecurity/trivy` | Go | All versions | 0.71.1 |
| `github.com/aquasecurity/trivy` | Go | All versions | 0.71.1 |
| `github.com/aquasecurity/trivy` | Go | All versions | 0.71.1 |

Products: Aquasec Trivy.

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

Upgrade github.com/aquasecurity/trivy to 0.71.1 or later.

## Is CVE-2026-55092 being exploited?

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

## Other vulnerabilities in aquasecurity trivy

- [CVE-2026-54448](https://insights.sbomify.com/CVE-2026-54448/): Trivy: Helm chart tar bomb causes OOM via unbounded io.ReadAll in parser (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55092 is a high-severity path traversal vulnerability in aquasecurity trivy, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-55092 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/aquasecurity/trivy (Go): affected all versions; fixed in 0.71.1
- github.com/aquasecurity/trivy (Go): affected all versions; fixed in 0.71.1
- github.com/aquasecurity/trivy (Go): affected all versions; fixed in 0.71.1

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-55092/ (Markdown: https://insights.sbomify.com/CVE-2026-55092/index.md)
```

## Sources

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

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