dbcve.org
TrivyApplication · Aquasec

CVE-2026-55092

HIGH · 7.5 CVSS v3.1 Published 2026-06-25
Fix available
A fix is available. Upgrade to 0.71.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Trivy uses the org.opencontainers.image.title annotation from OCI artifact manifests as the destination filename without validation. An attacker who can make Trivy fetch a crafted artifact can embed path traversal sequences (e.g., ../../../etc/cron.d/malicious) in this annotation, causing Trivy to write layer content to arbitrary host filesystem locations outside the intended directory.

MitigationUpgrade Trivy to version 0.71.1 or later, which implements validation of the annotation before using it as a destination filename. If immediate upgrade is not possible, restrict Trivy's network access to trusted OCI registries only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TrivyApplication
Affected:< 0.71.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Trivy version
    Run `trivy --version` or `trivy version` to identify the exact version number
    Affected if The installed version is less than 0.71.1 (for example, 0.70.0, 0.65.0, etc.)
  2. Identify OCI artifact scanning usage
    Review Trivy configuration files or command history for OCI registry scanning commands such as `trivy image <registry>/<artifact>`, `trivy oci`, or similar commands that fetch from OCI registries
    Affected if Trivy is configured to scan or fetch OCI artifacts from any registry (especially untrusted ones)
  3. Check for OCI artifact pull activity
    Examine Trivy logs, audit logs, or system logs for recent OCI artifact fetches. Look for commands using the `--artifact` flag or referencing OCI-compliant registries
    Affected if There are recent OCI artifact pull operations visible in logs or command history

Your environment is affected if Trivy version is below 0.71.1 AND the tool is being used to scan or fetch OCI artifacts from registries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.71.1 or later
Fixed in 0.71.1
Interim mitigation

Upgrade Trivy to version 0.71.1 or later, which implements validation of the annotation before using it as a destination filename. If immediate upgrade is not possible, restrict Trivy's network access to trusted OCI registries only.

Recommended fix High confidence

0.71.1

  1. Identify the current installed version of Trivy using `trivy --version`
  2. Download and install Trivy version 0.71.1 or later from the official release (e.g., https://github.com/aquasecurity/trivy/releases/tag/v0.71.1)
  3. Verify the upgrade was successful by running `trivy --version` and confirming it shows 0.71.1 or higher
  4. If using in automated pipelines or containers, update any Dockerfile, CI configuration, or container image references to use the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Trivy Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55092 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55092 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data