Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- High severity, with a CVSS score of 8.1, published 19 May 2026.
- Which products and versions are affected?
- land.oras:oras-java-sdk (Maven) <= 0.6.1.
- Is there a fix for This vulnerability?
- A patch was published on 2026-05-19: Fix available in version 0.6.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run land.oras:oras-java-sdk (Maven) or ORAS Project Java SDK at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in the `pullArtifact` methods of the `Registry` and `OCILayout` classes in ORAS Java. The library uses the `org.opencontainers.image.title` annotation from a pulled manifest as a filename without performing normalization or containment checks. By providing a title containing absolute paths or parent directory references (e.g., `../../`), an attacker-controlled registry can force the SDK to write or overwrite files anywhere the JVM process has write permissions. This issue is specifically present in the non-unpacking branch of `pullLayer` and in `OCILayout.pullArtifact`. The vulnerability is addressed in version 0.6.2.
Affected products
- ORAS Project oras-java-sdk <= 0.6.1
Timeline
- 2026-05-13: disclosed: Advisory published by reporter on GitHub
- 2026-05-19: advisory: GitHub Advisory reviewed and published
- 2026-05-19: patched: Fix available in version 0.6.2