CVE-2026-50163

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, ensureLinkPath in content/file/utils.go:262-275 validates a hardlink target relative to the extract base but returns the unresolved target, causing os.Link("victim.secret", "/payload.tar.gz/evil_cwd_link") to resolve header.Linkname against the process current working directory for a Typeflag=TypeLink entry such as Name=payload.tar.gz/evil_cwd_link and Linkname="victim.secret" with io.deis.oras.content.unpack: "true", which can expose or tamper with files such as .env, .git/config, .aws/credentials, and ~/.ssh/config. This issue is fixed in version 2.6.2.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
48(Track)
EG Risk 48/100SSVC: Track

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
Severity71% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 23, 2026

Advisory Details (4)

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

v2.6.2

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

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

commit c463c654ab3e (oras-project/oras-go)

Patch available: oras-project/oras-go v2.6.2 (contains commit c463c654ab3e)

https://github.com/oras-project/oras-go/commit/c463c654ab3ef34422c1764cd619806cebf20451
github_pr Patch Available

fix: prevent hardlink path traversal via process CWD (GHSA-fxhp-mv3v-67qp)

Patch available: oras-project/oras-go v2.6.2 (PR #1232 merged 2026-07-03)

https://github.com/oras-project/oras-go/pull/1232
github Patch Available🟡 PoC Available

Hardlink entry with relative Linkname escapes extract dir via process CWD resolution in `oras-go` tar extraction · Advisory · oras-project/oras-go · GitHub

https://github.com/oras-project/oras-go/security/advisories/GHSA-fxhp-mv3v-67qp

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatadvanced-cluster-security/rhacs-main-rhel8:17854209592026-07-30redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17854132102026-07-30redhat
gooras.land/oras-go/v2ghsa

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/v22.6.2

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 111× 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 148 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-50163?
CVE-2026-50163 is a high vulnerability published on July 1, 2026. oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, ensureLinkPath in content/file/utils.go:262-275 validates a hardlink target relative to the extract base but returns the unresolved target, causing os.Link("victim.secret", "<extractbase>/payload.tar.gz/evilcwdlink") to resolve…
When was CVE-2026-50163 disclosed?
CVE-2026-50163 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-50163 actively exploited?
CVE-2026-50163 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.3% of all scored CVEs.
What is the CVSS score of CVE-2026-50163?
CVE-2026-50163 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-50163?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50163, 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-50163

Explore →

Is Your Infrastructure Affected by CVE-2026-50163?

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