Vulnerability in oras.land/oras-go/v2 (CVE-2026-50162)
Summary
Vulnerability in oras.land/oras-go/v2 (CVE-2026-50162). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.6.1 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2026-50162 was discovered in oras.land/oras-go/v2.
Severity is Info. Low severity or not yet rated.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "oras.land/oras-go/v2 CVE-2026-50162".
CVE-2026-50162 (oras.land/oras-go/v2). Severity: Info. Category: CWE-73.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2026-50162) in oras.land/oras-go/v2. A serious software flaw has been identified.
Target versions of oras.land/oras-go/v2 (see vendor advisory). If running in production, identify exposure immediately.
Severity: Info. Low severity or not yet rated.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-73)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'oras.land/oras-go/v2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
oras.land/oras-go/v2を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade oras.land/oras-go/v2 to 2.6.1ステージング環境で 2.6.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-50162 golang-oras-oras-go
- Ubuntu UBUNTU-CVE-2026-50162 golang-oras-oras-go
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- web github.com
- web github.com