oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, content/file.Store extraction of OCI layers marked with io.deis.oras.content.unpack=true can write outside the store working directory. The pushDir path through extractTarDirectory and ensureLinkPath validates symlink targets lexically, resolveRelToBase skips its parent-symlink walk for root-level entries, and writeFile follows a terminal symlink when opening a regular file. A malicious archive can therefore create a symlink chain whose lexical target remains inside the extraction root but whose resolved target is an attacker-selected absolute path, then overwrite that target with a same-named regular-file entry even when AllowPathTraversalOnWrite is false. Pulling an attacker-controlled artifact can create or overwrite any file writable by the process and may lead to code execution. This issue is fixed in version 2.6.2.
CVE-2026-85731
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EG Risk
- 56(Track*)EG Risk 56/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 computedSeverity88% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 1%
- EPSS %ILE
- 50%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 16, 2026
Advisory Details (3)
Auto-updated Sep 16, 2026v2.6.2
Patch available: oras-project/oras-go v2.6.2
https://github.com/oras-project/oras-go/releases/tag/v2.6.2commit adab2f25ea95 (oras-project/oras-go)
Patch available: oras-project/oras-go v2.6.2 (contains commit adab2f25ea95)
https://github.com/oras-project/oras-go/commit/adab2f25ea95ef4e6e41f50db9266a6701399422Arbitrary file write outside file.Store root via symlink-chain bypass in tar extraction (pushDir) · Advisory · oras-project/oras-go · GitHub
https://github.com/oras-project/oras-go/security/advisories/GHSA-m37j-52j7-pjw7Vendor Advisories for CVE-2026-85731(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× 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.
- 2026-09-19 21:37 UTCEG score recompute
- 2026-09-18 20:37 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 07:54 UTCEG score recompute
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 18:24 UTCEG score recompute
- 2026-09-16 17:30 UTCEG score recompute
- 2026-09-16 16:36 UTCEG score recompute
- 2026-09-16 16:34 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-22 · CWE-59
Frequently asked(5)
What is CVE-2026-85731?
When was CVE-2026-85731 disclosed?
Is CVE-2026-85731 actively exploited?
What is the CVSS score of CVE-2026-85731?
How do I remediate CVE-2026-85731?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-85731
Is Your Infrastructure Affected by CVE-2026-85731?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.