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

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.9MEDIUMmedium confidence
EG Risk
62
EG Risk 62/100

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%
EPSS PROB
0.5%
EPSS %ILE
41st
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
githubMentions a patch (unverified)🟡 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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhem/flightctl-worker-rhel10:17894867402026-09-16redhat
redhatrhem/flightctl-worker-rhel9:17894868292026-09-16redhat
redhatrhem/flightctl-worker-rhel10:17894860712026-09-16redhat
redhatrhem/flightctl-worker-rhel9:17894880612026-09-16redhat
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 rangeFix by version rangeDependents
golang-oras-oras-go1.1.1-1, 2.5.0-1, 2.6.0-1, 2.6.2-1, 2.6.2-2
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-oras-oras-go2.5.0-1, 2.6.0-1, 2.6.2-1, 2.6.2-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-oras-oras-go2.5.0-1, 2.6.0-1
  • every version up to 2.6.2-1: fixed in 2.6.2-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
oras.land/oras-go/v2—
  • every version up to 2.6.1: fixed in 2.6.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 29× 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.

Showing the most recent 100 of 128 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-26 00:27 UTCEPSS rescore
  15. 2026-09-23 17:53 UTCEPSS rescore
  16. 2026-09-23 06:48 UTCEG score recompute
  17. 2026-09-23 06:48 UTCVendor advisory
  18. 2026-09-20 20:16 UTCEPSS rescore
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-18 06:28 UTCEG score recompute
  21. 2026-09-18 06:28 UTCVendor advisory
  22. 2026-09-16 14:08 UTCEPSS rescore
  23. 2026-09-16 05:15 UTCEPSS rescore
  24. 2026-09-14 00:21 UTCEG score recompute
  25. 2026-09-14 00:21 UTCVendor advisory
Show 75 more
  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 14:36 UTCEG score recompute
  3. 2026-09-12 14:36 UTCVendor advisory
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-10 09:35 UTCEPSS rescore
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-06 00:36 UTCEG score recompute
  10. 2026-09-06 00:36 UTCVendor advisory
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-09-01 04:40 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 11:34 UTCEG score recompute
  17. 2026-08-30 11:34 UTCVendor advisory
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 22:24 UTCEG score recompute
  21. 2026-08-27 22:24 UTCVendor advisory
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 16:15 UTCEG score recompute
  25. 2026-08-25 16:15 UTCVendor advisory
  26. 2026-08-25 13:49 UTCEPSS rescore
  27. 2026-08-24 10:49 UTCEG score recompute
  28. 2026-08-24 10:49 UTCVendor advisory
  29. 2026-08-23 09:09 UTCEG score recompute
  30. 2026-08-23 09:09 UTCVendor advisory
  31. 2026-08-23 00:19 UTCEPSS rescore
  32. 2026-08-22 07:37 UTCEG score recompute
  33. 2026-08-22 07:37 UTCVendor advisory
  34. 2026-08-21 23:49 UTCEPSS rescore
  35. 2026-08-21 06:06 UTCEG score recompute
  36. 2026-08-21 06:06 UTCVendor advisory
  37. 2026-08-20 22:55 UTCEPSS rescore
  38. 2026-08-20 04:35 UTCEG score recompute
  39. 2026-08-20 04:35 UTCVendor advisory
  40. 2026-08-19 17:04 UTCEPSS rescore
  41. 2026-08-18 20:57 UTCEG score recompute
  42. 2026-08-18 20:57 UTCVendor advisory
  43. 2026-08-18 13:48 UTCEPSS rescore
  44. 2026-08-17 14:11 UTCEG score recompute
  45. 2026-08-17 14:11 UTCVendor advisory
  46. 2026-08-17 13:47 UTCEPSS rescore
  47. 2026-08-16 14:56 UTCEPSS rescore
  48. 2026-08-16 12:41 UTCEG score recompute
  49. 2026-08-16 12:41 UTCVendor advisory
  50. 2026-08-16 02:14 UTCEPSS rescore
  51. 2026-08-15 11:10 UTCEG score recompute
  52. 2026-08-15 11:10 UTCVendor advisory
  53. 2026-08-15 01:30 UTCEPSS rescore
  54. 2026-08-14 09:39 UTCEG score recompute
  55. 2026-08-14 09:39 UTCVendor advisory
  56. 2026-08-13 22:00 UTCEPSS rescore
  57. 2026-08-13 08:08 UTCEG score recompute
  58. 2026-08-12 13:51 UTCEPSS rescore
  59. 2026-08-12 06:36 UTCEG score recompute
  60. 2026-08-11 05:05 UTCEG score recompute
  61. 2026-08-11 00:00 UTCEPSS rescore
  62. 2026-08-10 03:35 UTCEG score recompute
  63. 2026-08-09 13:46 UTCEPSS rescore
  64. 2026-08-09 02:04 UTCEG score recompute
  65. 2026-08-08 16:37 UTCEPSS rescore
  66. 2026-08-08 00:33 UTCEG score recompute
  67. 2026-08-06 23:03 UTCEG score recompute
  68. 2026-08-06 13:47 UTCEPSS rescore
  69. 2026-08-05 21:21 UTCEG score recompute
  70. 2026-08-05 19:17 UTCEPSS rescore
  71. 2026-08-04 19:51 UTCEG score recompute
  72. 2026-08-04 15:10 UTCEPSS rescore
  73. 2026-08-04 10:39 UTCEPSS rescore
  74. 2026-08-03 18:20 UTCEG score recompute
  75. 2026-08-03 10:36 UTCEPSS rescore

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 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 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50162?
CVE-2026-50162 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50162?
A fix for CVE-2026-50162 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50162 are linked in the Vendor Advisories panel on this page.

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.