CVE-2026-50162 oras-project CVE debrief

Who should care

Users of the oras-go library, particularly those who handle OCI artifacts, should be aware of this vulnerability and take steps to defend against it. This includes reviewing their deployments, validating and sanitizing user input, and implementing proper path traversal checks. Affected operators, platforms, and security teams should prioritize updating to version 2.6.1 or later.

Technical summary

The oras-go library, used for managing OCI artifacts, had a path traversal vulnerability prior to version 2.6.1. The resolveWritePath() function in content/file/file.go did not account for symlink traversal, allowing an attacker to create files outside the working directory. This issue was fixed in version 2.6.1. Users of the oras-go library, particularly those who handle OCI artifacts, should be aware of this vulnerability and take steps to defend against it.

Defensive priority

Medium

Recommended defensive actions

• Update oras-go to version 2.6.1 or later
• Validate and sanitize user input
• Implement proper path traversal checks
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability. Further investigation and testing may be necessary to fully understand the impact and defend against it. The oras-go library, used for managing OCI artifacts, had a path traversal vulnerability prior to version 2.6.1. The resolveWritePath() function in content/file/file.go did not account for symlink traversal, allowing an attacker to create files outside the working directory. Users should verify their deployments and review the official advisory for affected scope and vendor guidance.

Official resources