How severe is CVE-2026-55092?

No CVSS score has been assigned to CVE-2026-55092 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-55092?

CVE-2026-55092 affects the following packages: github.com/aquasecurity/trivy (Go). Ecosystems affected: Go.

How do I fix CVE-2026-55092?

Update github.com/aquasecurity/trivy to 0.71.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-55092 is resolved across your whole dependency graph.

How do I detect CVE-2026-55092 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/aquasecurity/trivy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-55092 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-55092 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-55092 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-55092?

CVE-2026-55092 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-55092?

CVE-2026-55092 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-55092 published, and has it been updated?

CVE-2026-55092 was published on June 25, 2026 and was last updated on September 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2026-55092 — trivy

Fix: aquasecurity/trivy@39e0b13

CVE-2026-55092 is a Path Traversal vulnerability in github.com/aquasecurity/trivy. A fix is available for github.com/aquasecurity/trivy — see the affected versions and patch details below.

Trivy: Path traversal via a crafted vulnerability database or other downloaded artifacts

Also known asGHSA-mcj4-mphf-j9ffGO-2026-6294

Published

Jun 25, 2026

Updated

Sep 29, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-55092.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/aquasecurity/trivy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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.

Affected configurations

Exploitation requires the attacker to direct Trivy at an attacker-controlled OCI artifact via one of the following inputs:

Input	Used for
`--db-repository` flag, `TRIVY_DB_REPOSITORY` environment variable, or `db.repository` in `trivy.yaml`	Vulnerability database
`--java-db-repository` flag, `TRIVY_JAVA_DB_REPOSITORY` environment variable, or `db.java-repository` in `trivy.yaml`	Java vulnerability database
`--checks-bundle-repository` flag (and the deprecated `--policy-bundle-repository` alias), `TRIVY_CHECKS_BUNDLE_REPOSITORY` environment variable, or `misconfiguration.checks-bundle-repository` in `trivy.yaml`	Misconfiguration checks bundle
Repository argument to `trivy module install <REPO>`	WASM module installation

Realistic scenarios in which an attacker may influence these inputs include a copy-pasted command or documentation snippet pointing to an untrusted mirror, or a third-party mirror that turns out to be hostile.

Trivy's default configuration, which downloads these artifacts from Aqua-operated repositories, is not affected. The risk applies only when one of the inputs above is overridden to download a different artifact.

Impact

An attacker who satisfies the conditions above can overwrite or create arbitrary files on the host filesystem within the privilege boundary of the user running Trivy. The vulnerability does not grant any privileges beyond what that user already has.

The practical impact depends on the deployment. In environments where the running user can overwrite files such as SSH authorized_keys, shell startup files, cron entries, or binaries on PATH, the file write may be leveraged to achieve code execution as that user. In more restricted deployments, the impact is bounded to the user's writable scope but may still allow tampering with scan results, build artifacts, or other files consumed by subsequent steps in the same pipeline.

Patches

Fixed in Trivy 0.71.1. Users should upgrade to that release or later.

Workarounds

If upgrading is not immediately possible, do not download Trivy artifacts (vulnerability database, Java database, misconfiguration checks bundle, modules, etc.) from OCI repositories you do not operate or trust.

Credits

Reported by @ikkebr.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/aquasecurity/trivy`	all versions	0.71.1`go get github.com/aquasecurity/trivy@v0.71.1`

Affected Products

1 product · 1 configurations

Application

trivyaquasec

< 0.71.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/aquasecurity/trivy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/aquasecurity/trivy to 0.71.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-55092 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

## Summary 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. ## Affected configurations Exploitation requires the attacker to direct Trivy at an attacker-controlled OCI artifact via one of the following inputs: | Input | Used fo

O3 Security · Impact-Aware SCA

Is CVE-2026-55092 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works