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 59% 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.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.9Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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 PROB
1%
EPSS %ILE
41%
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(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhathelm4-main-4.2.3-0.1.2.hum12026-07-20redhat
redhathelm3-main-3.21.3-0.1.2.hum12026-07-20redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-oras-oras-go1.1.1-1, 2.5.0-1, 2.6.0-1, 2.6.2-1——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-oras-oras-go2.5.0-1, 2.6.0-1, 2.6.2-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-oras-oras-go2.5.0-1, 2.6.0-12.6.2-1—
Go(1)
PackageVulnerable rangeFixed inDependents
oras.land/oras-go/v2—2.6.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 63× 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-08-25 16:15 UTCEG score recompute
  2. 2026-08-25 16:15 UTCVendor advisory
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-24 10:49 UTCEG score recompute
  5. 2026-08-24 10:49 UTCVendor advisory
  6. 2026-08-23 09:09 UTCEG score recompute
  7. 2026-08-23 09:09 UTCVendor advisory
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 07:37 UTCEG score recompute
  10. 2026-08-22 07:37 UTCVendor advisory
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 06:06 UTCEG score recompute
  13. 2026-08-21 06:06 UTCVendor advisory
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-20 04:35 UTCEG score recompute
  16. 2026-08-20 04:35 UTCVendor advisory
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 20:57 UTCEG score recompute
  19. 2026-08-18 20:57 UTCVendor advisory
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 14:11 UTCEG score recompute
  22. 2026-08-17 14:11 UTCVendor advisory
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 12:41 UTCEG score recompute
Show 55 more
  1. 2026-08-16 12:41 UTCVendor advisory
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 11:10 UTCEG score recompute
  4. 2026-08-15 11:10 UTCVendor advisory
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 09:39 UTCEG score recompute
  7. 2026-08-14 09:39 UTCVendor advisory
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 08:08 UTCEG score recompute
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 06:36 UTCEG score recompute
  12. 2026-08-11 05:05 UTCEG score recompute
  13. 2026-08-11 00:00 UTCEPSS rescore
  14. 2026-08-10 03:35 UTCEG score recompute
  15. 2026-08-09 13:46 UTCEPSS rescore
  16. 2026-08-09 02:04 UTCEG score recompute
  17. 2026-08-08 16:37 UTCEPSS rescore
  18. 2026-08-08 00:33 UTCEG score recompute
  19. 2026-08-06 23:03 UTCEG score recompute
  20. 2026-08-06 13:47 UTCEPSS rescore
  21. 2026-08-05 21:21 UTCEG score recompute
  22. 2026-08-05 19:17 UTCEPSS rescore
  23. 2026-08-04 19:51 UTCEG score recompute
  24. 2026-08-04 15:10 UTCEPSS rescore
  25. 2026-08-04 10:39 UTCEPSS rescore
  26. 2026-08-03 18:20 UTCEG score recompute
  27. 2026-08-03 10:36 UTCEPSS rescore
  28. 2026-08-02 15:54 UTCEG score recompute
  29. 2026-08-02 02:27 UTCEPSS rescore
  30. 2026-08-01 14:23 UTCEG score recompute
  31. 2026-08-01 04:16 UTCEPSS rescore
  32. 2026-07-31 12:52 UTCEG score recompute
  33. 2026-07-30 16:28 UTCEPSS rescore
  34. 2026-07-30 11:19 UTCEG score recompute
  35. 2026-07-30 01:30 UTCEPSS rescore
  36. 2026-07-29 09:45 UTCEG score recompute
  37. 2026-07-28 15:37 UTCEPSS rescore
  38. 2026-07-28 08:14 UTCEG score recompute
  39. 2026-07-27 06:42 UTCEG score recompute
  40. 2026-07-26 14:54 UTCEPSS rescore
  41. 2026-07-26 05:10 UTCEG score recompute
  42. 2026-07-25 14:18 UTCEPSS rescore
  43. 2026-07-24 14:18 UTCEPSS rescore
  44. 2026-07-23 14:18 UTCEPSS rescore
  45. 2026-07-23 03:18 UTCEG score recompute
  46. 2026-07-22 14:08 UTCEPSS rescore
  47. 2026-07-21 15:25 UTCEPSS rescore
  48. 2026-07-20 17:08 UTCEPSS rescore
  49. 2026-07-19 14:31 UTCEPSS rescore
  50. 2026-07-19 14:31 UTCEPSS rescore
  51. 2026-07-19 03:51 UTCEG score recompute
  52. 2026-07-19 02:29 UTCEPSS rescore
  53. 2026-07-17 19:50 UTCEG score recompute▲ 6.90
  54. 2026-07-17 19:49 UTCMITRE cvelistV5CVSS v3 → 6.9 · CVSS v4 → 6.9
  55. 2026-07-01 22:02 UTCEG score recompute

Related CVEs(same vendor + same CWE)

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 1% probability of exploitation in the next 30 days, which ranks it in the top 59.0% of all scored CVEs.
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.

Start Free Scan →Browse All CVEs