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
Elevated
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.3%CVSS: 7.1Exploit: 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.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.1HIGHmedium confidence
EG Risk
48
EG Risk 48/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
Severity71% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.3%
EPSS %ILE
26th
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
githubMentions a patch (unverified)🟡 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 / EcosystemFix (by version range) / PatchReleasedSource
redhatadvanced-cluster-security/rhacs-main-rhel8:17854209592026-07-30redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17854132102026-07-30redhat
gooras.land/oras-go/v2—ghsa

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.2: fixed in 2.6.2
—

Weakness Classification(2)

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

Data Freshness Timeline

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

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 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.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50163?
CVE-2026-50163 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50163?
A fix for CVE-2026-50163 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50163 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-50163

Explore →

Is Your Infrastructure Affected by CVE-2026-50163?

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