How severe is CVE-2026-17106?

No CVSS score has been assigned to CVE-2026-17106 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-17106?

CVE-2026-17106 affects the following packages: github.com/moby/go-archive (Go). Ecosystems affected: Go.

How do I fix CVE-2026-17106?

Update github.com/moby/go-archive to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-17106 is resolved across your whole dependency graph.

How do I detect CVE-2026-17106 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/moby/go-archive, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-17106 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-17106 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2026-17106, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2026-17106?

CVE-2026-17106 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-17106?

CVE-2026-17106 is classified as CWE-59 (CWE-59). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-17106 published, and has it been updated?

CVE-2026-17106 was published on August 18, 2026 and was last updated on September 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2026-17106 — go-archive

CVE-2026-17106 is a CWE-59 vulnerability in github.com/moby/go-archive. 1 public exploit reference exists, so weaponization risk is real. A fix is available for github.com/moby/go-archive — see the affected versions and patch details below.

Tar extraction in moby/go-archive can write outside the destination directory via link following

Also known asBIT-docker-cli-2026-17106GHSA-hfg8-hc9c-6c3hGO-2026-6253

Published

Aug 18, 2026

Updated

Sep 29, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-17106.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.12%

Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/moby/go-archive

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the ApplyLayer helpers) do not confine filesystem operations to the destination directory. A crafted archive can create or overwrite files outside the intended destination.

Details

The extractor decides where each archive entry lands using lexical string checks and then performs the filesystem operation on a path that is resolved by the OS, so a links introduced by the archive can be followed out of the destination directory.

Impact

An attacker who controls the contents of archive can create or overwrite files at arbitrary paths writable by the extracting process.

Workarounds

Only extract trusted archives.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/moby/go-archive`	all versions	0.3.0`go get github.com/moby/go-archive@v0.3.0`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

masasron/CopyEscape-CVE-2026-17106

PoC repository for the blog post CopyEscape: Taking Over Docker Hosts wi

⭐ 21🍴 3Sep 2026

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/moby/go-archive, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/moby/go-archive to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-17106 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This Important severity vulnerability in `moby/go-archive` allows for arbitrary file writes during tar extraction. An attacker providing a specially crafted tar archive can exploit symlink following to create or overwrite files outside the intended directory, potentially leading to system compromise in environments…

Workaround published by Red Hat

To mitigate this issue, avoid processing tar archives from untrusted sources. When handling archives from potentially untrusted origins, ensure that the extraction process is executed with the least privileges necessary to limit the impact of any arbitrary file write attempts.

Source: Red Hat security advisory for CVE-2026-17106 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Enterprise Linux 10	`podman-7:5.8.2-9.el10_2`	RHSA-2026:70201
Red Hat Enterprise Linux 9	`podman-6:5.8.2-7.el9_8`	RHSA-2026:69961
Logging Subsystem for Red Hat OpenShift 6.6	`openshift-logging/cluster-logging-rhel9-operator:1788439505`	RHSA-2026:66521
Multicluster Global Hub 1.8.2	`multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1788441983`	RHSA-2026:68515
Multicluster Global Hub 1.8.2	`multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1790639009`	RHSA-2026:73038
Red Hat Advanced Cluster Management for Kubernetes 2.17	`rhacm2/acm-grafana-rhel9:1790240693`	RHSA-2026:72879
Red Hat Edge Manager 1.2	`rhem/flightctl-alert-exporter-rhel10:1789485358`	RHSA-2026:68006
Red Hat Edge Manager 1.2	`rhem/flightctl-alert-exporter-rhel9:1789485374`	RHSA-2026:68254

Frequently Asked Questions

### Summary The tar extraction routines in `moby/go-archive` (`Unpack`, `UnpackLayer`, `Untar`/`UntarUncompressed`, and the `ApplyLayer` helpers) do not confine filesystem operations to the destination directory. A crafted archive can create or overwrite files **outside** the intended destination. ### Details The extractor decides where each archive entry lands using lexical string checks and then performs the filesystem operation on a path that is resolved by the OS, so a links introduced by the archive can be followed out of the destination directory. ### Impact An attacker who controls t

O3 Security · Impact-Aware SCA

Is CVE-2026-17106 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works