cve.bz

CVE-2026-17106 (CopyEscape) Link Following

7.1 highEPSS 0.5%Fix available

Known as CopyEscape

High (7.1). EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/moby/go-archive 0.3.0.

On this page
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. 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 links introduced by the archive can be followed out of the destination directory. An attacker who controls the contents of an archive can create or overwrite files at arbitrary paths writable by the extracting process.

Severity

CVSS 4.0

7.1 high
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
EPSS
0.5% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 42nd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-08-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-17106 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-17106?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-17106?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-17106 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
moby go-archivebefore 0.3.0
Docker Sandboxesbefore 0.38.0
Docker Desktopbefore 4.86.0
Docker Enginebefore 29.7.0
Docker CLIbefore 29.7.0
Docker Composebefore 5.4.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-hfg8-hc9c-6c3hGogithub.com/moby/go-archive<0.3.00.3.0
GO-2026-6253Gogithub.com/moby/go-archive<0.3.00.3.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14golang-github-moby-go-archive0.3.3-1DEBIAN-CVE-2026-17106
Ubuntu26.04:LTS, 26.10, Pro:20.04:LTS and 2 moredocker.io, docker.io-appno fix listedUBUNTU-CVE-2026-17106
UbuntuPro:16.04:LTS, Pro:18.04:LTSdocker.iono fix listedUBUNTU-CVE-2026-17106
Red Hathummingbird:1podman, podmansh, podman-docker and 2 more5:6.0.2-2.2.hum1RHSA-2026:52807
SUSELinux Enterprise Module for HPC 15 SP7, Linux Enterprise Module for Package Hub 15 SP7, Linux Enterprise Server 15 SP6-LTSSapptainer1.5.3-150600.4.37.1SUSE-SU-2026:3863-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20260827T195228-160000.1.1SUSE-SU-2026:23625-1
openSUSELeap 16.0apptainer1.5.3-bp160.2.1openSUSE-SU-2026:21611-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260827T195228-160000.1.1openSUSE-SU-2026:21761-1
openSUSETumbleweedapptainer1.5.3-2.1openSUSE-SU-2026:11544-1
openSUSETumbleweedbuildah1.46.0-1.1openSUSE-SU-2026:12341-1
openSUSETumbleweedbuildpacks-cli0.40.10-1.1openSUSE-SU-2026:12260-1
openSUSETumbleweedpodman6.1.2-1.1openSUSE-SU-2026:12068-1
AlmaLinux9podman, podman-tests, podman-docker and 2 more6:5.8.2-7.el9_8ALSA-2026:69961
AlmaLinux10podman, podman-tests, podman-docker and 1 more7:6.1.1-1.el10_3.alma.1ALSA-2026:98554
AlmaLinux10podman-docker7:5.8.2-9.el10_2.alma.1ALSA-2026:70201
Rocky Linux9podman6:5.8.2-7.el9_8RLSA-2026:69961
Rocky Linux10podman7:5.8.2-9.el10_2RLSA-2026:70201
Rocky Linux10podman, podman-tests, podman-docker and 5 more7:6.1.1-1.el10_3RLSA-2026:98554
Azure Linux3docker-cli25.0.7-5AZL-97004
Azure Linux3moby-engine25.0.3-20AZL-97007
Alpaquita23, 25podman5.6.2-r13BELL-CVE-2026-17106
Alpaquita25buildah1.41.8-r8BELL-CVE-2026-17106
Alpaquita25docker-cli-buildx0.24.0-r15BELL-CVE-2026-17106
Alpaquitastreambuildah1.44.0-r6BELL-CVE-2026-17106
Alpaquitastreamdocker-cli-buildx0.36.1-r3BELL-CVE-2026-17106
Alpaquitastreampodman5.8.6-r3BELL-CVE-2026-17106

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

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 processing untrusted archives, such as container build systems.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10podman-7:5.8.2-9.el10_2Fixed 2026-09-22RHSA-2026:70201
Red Hat Enterprise Linux 10rhel10/podman:7:5.8.2-9.el10_2Fixed 2026-09-22RHSA-2026:70201
Red Hat Enterprise Linux 10ubi10/podman:7:5.8.2-9.el10_2Fixed 2026-09-22RHSA-2026:70201
Red Hat Enterprise Linux 10podman-7:6.1.1-1.el10_3Fixed 2026-11-11RHSA-2026:98554
Red Hat Enterprise Linux 10rhel10/podman:7:6.1.1-1.el10_3Fixed 2026-11-11RHSA-2026:98554
Red Hat Enterprise Linux 10ubi10/podman:7:6.1.1-1.el10_3Fixed 2026-11-11RHSA-2026:98554
Red Hat Enterprise Linux 9podman-6:5.8.2-7.el9_8Fixed 2026-09-22RHSA-2026:69961
Logging Subsystem for Red Hat OpenShift 6.6openshift-logging/cluster-logging-rhel9-operator:1788439505Fixed 2026-09-10RHSA-2026:66521
Multicluster Global Hub 1.8.2multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1788441983Fixed 2026-09-17RHSA-2026:68515
Multicluster Global Hub 1.8.2multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1790639009Fixed 2026-09-29RHSA-2026:73038
Confidential Compute Attestationopenshift-sandboxed-containers/osc-must-gather-rhel9Not affected
Confidential Compute Attestationopenshift-sandboxed-containers/osc-podvm-builder-rhel9Not affected
Confidential Compute Attestationopenshift-sandboxed-containers/osc-rhel9-operatorNot affected
Cryostat 4cryostat/cryostat-storage-rhel9Not affected
DPU kit for NVIDIAdpu-kit-for-nvidia/must-gather-rhel10Affected
Kernel Module Management Operator for Red Hat Openshiftkmm/kernel-module-management-must-gather-rhel9Affected
Multicluster Engine for Kubernetesmulticluster-engine/assisted-installer-agent-rhel8Will not fix
Multicluster Engine for Kubernetesmulticluster-engine/assisted-installer-agent-rhel9Affected
Multicluster Engine for Kubernetesmulticluster-engine/assisted-installer-controller-rhel8Will not fix
Multicluster Engine for Kubernetesmulticluster-engine/assisted-installer-controller-rhel9Affected
139 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-17106.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • masasron/CopyEscape-CVE-2026-17106 Harbor Check: matches CVE 24 stars, C, created
    PoC repository for the blog post CopyEscape: Taking Over Docker Hosts with docker cp
  • 686f6c61/POC-CopyEscape-CVE-2026-17106 Harbor Check: matches CVE 1 star, C, created
    PoC funcional de CVE-2026-17106 (CopyEscape): carrera TOCTOU en docker cp que permite escritura arbitraria en el host Docker. Laboratorio D…
  • HackSpeak/CVE-2026-17106 Harbor Check: matches CVE 1 star, C, created
    CopyEscape (CVE-2026-17106) docker cp container-to-host arbitrary file write PoC mirror — Imperva Ron Masas, MIT; for authorized security t…

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON