ORAS Java: Path traversal in pullArtifact via attacker-controlled org.opencontainers.image.title annotation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary The pullArtifact methods in Registry and OCILayout use the org.opencontainers.image.title annotation from a pulled manifest as a filename, resolving it against the caller supplied output directory without normalization or a containment check. A manifest publisher can set this annotation to a path that escapes the output directory, causing the SDK to write the layer's blob anywhere the JVM process can write. Details Two call sites are affected. src/main/java/land/oras/Registry.java, pullLayer (reached from Registry.pullArtifact): src/main/java/land/oras/OCILayout.java, OCILayout.pullArtifact: The annotation comes from the remote manifest. Path.resolve treats an absolute argument as a full override of the base, and follows .. segments upward, so the annotation controls the destination. REPLACEEXISTING overwrites files that exist at that destination. The unpack branch of pullLayer (taken when the layer carries io.deis.oras.content.unpack=true) is not affected, because it…

Published by the source

19 May 2026, 15:47 UTC

Last modified by the source

19 May 2026, 15:47 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xm96-gfjx-jcrc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-xm96-gfjx-jcrc

Advisory: ORAS Java: Path traversal in pullArtifact via attacker-controlled org.opencontainers.image.title annotation
IDs: GHSA-xm96-gfjx-jcrc
Record: https://patchnext.com/advisories/ghsa-xm96-gfjx-jcrc (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: land.oras:oras-java-sdk 0.6.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven land.oras:oras-java-sdk: affected <= 0.6.1; fixed in 0.6.2

## Suggested inspection (read-only)
- Maven land.oras:oras-java-sdk: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on land.oras:oras-java-sdk.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xm96-gfjx-jcrc (GitHub-reviewed advisory GHSA-xm96-gfjx-jcrc lists affected ranges: Maven land.oras:oras-java-sdk >=0 <=0.6.1)

Commands are suggestions: review each one before running it.