Skip to main content
VulnerabilityPublished

CVE-2026-85731: oras-go · Path Traversal

Affects oras-goSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 2.6.2 soon.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.6.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Upgrade oras-go and github.com/oras-project/oras-go to 2.6.2.

Affected software

ProductAffectedFixed in
oras-projectoras-goAffected
  • <2.6.2
Fixed in
  • 2.6.2
Gogithub.com/oras-project/oras-gopkg:golang/github.com/oras-project/oras-goOther threatsAffected
  • <2.6.2
Fixed in
  • 2.6.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to oras-go version 2.6.2 or later, where this path traversal vulnerability is fixed. No other mitigations are specified. Patch status is confirmed by the vendor advisory stating the issue is fixed in 2.6.2.

Description

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.

References

Community reviews

Loading reviews…