CVE-2026-55092High· 7.5▾ TwilightTrivy has a path traversal via a crafted vulnerability database or other downloaded artifacts
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 41.3 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Aug 25.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via GHSA
0.4%
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.
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.
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.
Fixed in Trivy 0.71.1. Users should upgrade to that release or later.
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.
Reported by @ikkebr.
github.com/aquasecurity/trivy < 0.71.1Upgrade to a patched release:
github.com/aquasecurity/trivy 0.71.1Connected by shared product, vendor, weakness, or advisory.
CVE-2026-63328MediumTrivy is a security scanner
CVE-2026-33634CriticalTrivy ecosystem supply chain was briefly compromised
CVE-2026-54448HighTrivy: Helm chart tar bomb causes OOM via unbounded io.ReadAll in parser
CVE-2022-37906Medium· 6.5An authenticated path traversal vulnerability exists in the ArubaOS command line interface
CVE-2024-13986High· 8.8Nagios XI < 2024R1.3.2 contains a remote code execution vulnerability by chaining two flaws: an arbitrary file upload and a path traversal in the Core Config Snapshots interface
CVE-2023-7260High· 7.5Path Traversal vulnerability discovered in OpenText™ CX-E Voice, affecting all version through 22.4