CVE-2026-50162: CWE-73: External Control of File Name or Path in oras-project oras-go
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.
AI Analysis
Technical Summary
The oras-go library, used for managing OCI artifacts, contains a vulnerability in the resolveWritePath() function located in content/file/file.go. Before version 2.6.1, this function uses a lexical filepath.Rel check to validate paths relative to workingDir but does not account for symlink traversal. Consequently, if AllowPathTraversalOnWrite is set to false, an attacker can craft a blob title (via ocispec.AnnotationTitle) such as 'out/pwn.txt' where 'out' is a symlink pointing outside the working directory. This allows pushFile() to write files outside the intended directory, leading to external control of file paths. The vulnerability is addressed in version 2.6.1.
Potential Impact
An attacker with the ability to control the blob title can cause files to be written outside the designated working directory by exploiting symlink traversal. This can lead to unauthorized file creation or overwriting in arbitrary locations on the filesystem, potentially impacting system integrity or security. The CVSS 4.0 base score is 6.9 (medium severity), indicating a significant but not critical risk.
Mitigation Recommendations
This vulnerability is fixed in oras-go version 2.6.1. Users should upgrade to version 2.6.1 or later to remediate this issue. No other official remediation or temporary fixes are documented. Patch status is confirmed by the vendor advisory stating the fix in 2.6.1.
CVE-2026-50162: CWE-73: External Control of File Name or Path in oras-project oras-go
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.
CVSS v4.0
Score 6.9medium
Affected software
pkg:golang/github.com/oras-project/oras-goRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The oras-go library, used for managing OCI artifacts, contains a vulnerability in the resolveWritePath() function located in content/file/file.go. Before version 2.6.1, this function uses a lexical filepath.Rel check to validate paths relative to workingDir but does not account for symlink traversal. Consequently, if AllowPathTraversalOnWrite is set to false, an attacker can craft a blob title (via ocispec.AnnotationTitle) such as 'out/pwn.txt' where 'out' is a symlink pointing outside the working directory. This allows pushFile() to write files outside the intended directory, leading to external control of file paths. The vulnerability is addressed in version 2.6.1.
Potential Impact
An attacker with the ability to control the blob title can cause files to be written outside the designated working directory by exploiting symlink traversal. This can lead to unauthorized file creation or overwriting in arbitrary locations on the filesystem, potentially impacting system integrity or security. The CVSS 4.0 base score is 6.9 (medium severity), indicating a significant but not critical risk.
Mitigation Recommendations
This vulnerability is fixed in oras-go version 2.6.1. Users should upgrade to version 2.6.1 or later to remediate this issue. No other official remediation or temporary fixes are documented. Patch status is confirmed by the vendor advisory stating the fix in 2.6.1.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-03T20:54:20.432Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5b5eb02d1edb114c7fb351
Added to database: 07/18/2026, 11:08:32 UTC
Last enriched: 07/25/2026, 22:46:05 UTC
Last updated: 08/31/2026, 22:52:12 UTC
Views: 57
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.