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.
CVE-2026-50163
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.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- 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 computedSeverity71% × 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, 2026v2.6.2
Patch available: oras-project/oras-go v2.6.2
https://github.com/oras-project/oras-go/releases/tag/v2.6.2commit 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/c463c654ab3ef34422c1764cd619806cebf20451fix: 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/1232Hardlink 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-67qpVendor Advisories for CVE-2026-50163(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:48913Red Hat Product SecurityHigh
Red Hat Security Advisory: RHACS 4.10.6 security and bug fix update
- RHSA-2026:48872Red Hat Product SecurityHigh
Red Hat Security Advisory: RHACS 4.9.10 security and bug fix update
- GHSA-fxhp-mv3v-67qpGitHub Security AdvisoriesHigh
`oras-go` tar extraction: Hardlink entry with relative Linkname escapes extract dir via process CWD resolution
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | advanced-cluster-security/rhacs-main-rhel8:1785420959 | 2026-07-30 | redhat |
| redhat | advanced-cluster-security/rhacs-main-rhel8:1785413210 | 2026-07-30 | redhat |
| go | oras.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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-oras-oras-go | 1.1.1-1, 2.5.0-1, 2.6.0-1, 2.6.2-1 | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-oras-oras-go | 2.5.0-1, 2.6.0-1, 2.6.2-1 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-oras-oras-go | 2.5.0-1, 2.6.0-1 | 2.6.2-1 | — |
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| oras.land/oras-go/v2 | — | 2.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.
- 2026-08-21 06:59 UTCEG score recompute
- 2026-08-21 06:59 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 17:44 UTCVendor advisory
- 2026-08-20 04:35 UTCEG score recompute
- 2026-08-20 04:35 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 10:18 UTCVendor advisory
- 2026-08-18 20:57 UTCEG score recompute
- 2026-08-18 20:57 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 23:18 UTCEG score recompute
- 2026-08-17 23:18 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 08:54 UTCVendor advisory
- 2026-08-16 19:46 UTCEG score recompute
- 2026-08-16 19:46 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 06:15 UTCEG score recompute
- 2026-08-16 06:15 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 17:08 UTCVendor advisory
- 2026-08-15 04:00 UTCEG score recompute
- 2026-08-15 04:00 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-14 14:52 UTCVendor advisory
- 2026-08-14 01:44 UTCEG score recompute
- 2026-08-14 01:44 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 12:36 UTCVendor advisory
- 2026-08-12 23:28 UTCEG score recompute
- 2026-08-12 23:28 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 10:21 UTCVendor advisory
- 2026-08-11 21:12 UTCEG score recompute
- 2026-08-11 21:12 UTCVendor advisory
- 2026-08-11 08:04 UTCEG score recompute
- 2026-08-11 08:04 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 18:57 UTCVendor advisory
- 2026-08-10 05:49 UTCVendor advisory
- 2026-08-09 16:42 UTCEG score recompute
- 2026-08-09 16:42 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 03:34 UTCEG score recompute
- 2026-08-09 03:34 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 14:26 UTCVendor advisory
- 2026-08-08 01:18 UTCEG score recompute
- 2026-08-08 01:18 UTCVendor advisory
- 2026-08-07 12:10 UTCVendor advisory
- 2026-08-06 23:03 UTCEG score recompute
- 2026-08-06 23:03 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 09:27 UTCVendor advisory
- 2026-08-05 20:19 UTCEG score recompute
- 2026-08-05 20:19 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 07:12 UTCVendor advisory
- 2026-08-04 15:22 UTCEG score recompute
- 2026-08-04 15:22 UTCVendor advisory
- 2026-08-04 15:22 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 02:14 UTCVendor advisory
- 2026-08-04 02:14 UTCGHSA enrichment
- 2026-08-03 13:06 UTCEG score recompute
- 2026-08-03 13:06 UTCVendor advisory
- 2026-08-03 13:06 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 22:48 UTCVendor advisory
- 2026-08-02 22:48 UTCGHSA enrichment
- 2026-08-02 09:40 UTCEG score recompute
- 2026-08-02 09:40 UTCVendor advisory
- 2026-08-02 09:40 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 20:31 UTCVendor advisory
- 2026-08-01 20:31 UTCGHSA enrichment
- 2026-08-01 07:23 UTCEG score recompute
- 2026-08-01 07:23 UTCVendor advisory
- 2026-08-01 07:23 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 17:26 UTCVendor advisory
- 2026-07-31 17:25 UTCGHSA enrichment
- 2026-07-31 04:17 UTCEG score recompute
- 2026-07-31 04:17 UTCVendor advisory
- 2026-07-31 04:17 UTCGHSA enrichment
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 15:07 UTCEG score recompute
- 2026-07-30 15:07 UTCGHSA enrichment
- 2026-07-30 01:59 UTCEG score recompute
- 2026-07-30 01:59 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 12:48 UTCGHSA enrichment
- 2026-07-28 23:40 UTCEG score recompute
- 2026-07-28 23:40 UTCGHSA enrichment
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 10:05 UTCGHSA enrichment
- 2026-07-27 20:54 UTCEG score recompute
- 2026-07-27 20:54 UTCGHSA enrichment
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-22 · CWE-59
Frequently asked(5)
What is CVE-2026-50163?
When was CVE-2026-50163 disclosed?
Is CVE-2026-50163 actively exploited?
What is the CVSS score of CVE-2026-50163?
How do I remediate CVE-2026-50163?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50163
Is Your Infrastructure Affected by CVE-2026-50163?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.