CVE-2026-50162

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
6.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 6.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
6.9
EG Score
6.9(medium)
EG Risk
62(Attend)
EG Risk 62/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity69% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
40.2%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jul 17, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github_release Patch Available

v2.6.1

Patch available: oras-project/oras-go v2.6.1

https://github.com/oras-project/oras-go/releases/tag/v2.6.1
github_commit Patch Available

commit cc323e564d90 (oras-project/oras-go)

Patch available: oras-project/oras-go v2.6.1 (contains commit cc323e564d90)

https://github.com/oras-project/oras-go/commit/cc323e564d90c6b5b4bdd71d3c8d2ee2713b37e5
github Patch Available🟡 PoC Available

file store write outside workingDir via symlink traversal in oras-go · Advisory · oras-project/oras-go · GitHub

https://github.com/oras-project/oras-go/security/advisories/GHSA-8xwf-rjm4-xvhv

Vendor Advisories for CVE-2026-50162(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
oras.land/oras-go/v22.6.1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:18 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 03:51 UTCEG score recompute
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-17 19:50 UTCEG score recompute 6.90
  11. 2026-07-17 19:49 UTCMITRE cvelistV5CVSS v3 → 6.9 · CVSS v4 → 6.9
  12. 2026-07-01 22:02 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-50162?
CVE-2026-50162 is a medium vulnerability published on July 1, 2026. 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…
When was CVE-2026-50162 disclosed?
CVE-2026-50162 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50162 actively exploited?
CVE-2026-50162 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50162?
CVE-2026-50162 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-50162?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50162, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50162

Explore →

Is Your Infrastructure Affected by CVE-2026-50162?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.