
oras-go checked the name, not where it led. A symlink in the directory, and a file named out/impact.txt lands outside it. CVE-2026-50162. We blocked it at runtime without touching ORAS. Refused, and ORAS kept running.
Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
oras-go is a Go library for managing OCI artifacts. Prior to 2.6.1, resolveWritePath() in content/file/file.go uses a lexical filepath.Rel check for workingDir and does not account for symlink traversal, so when AllowPathTraversalOnWrite=false an attacker-controlled blob title through ocispec.AnnotationTitle such as out/pwn.txt can follow a workingDir symlink out -> /some/outside/dir and cause pushFile() to create /some/outside/dir/pwn.txt outside workingDir. This issue is fixed in version 2.6.1.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
NONE

oras-go checked the name, not where it led. A symlink in the directory, and a file named out/impact.txt lands outside it. CVE-2026-50162. We blocked it at runtime without touching ORAS. Refused, and ORAS kept running.