# CVE-2026-17106: Tar extraction in moby/go-archive can write outside the destination directory via link following > Attackers can write files outside the destination directory via malicious tar archives, potentially leading to arbitrary file overwrite or code execution in Docker environments. - **Severity:** High 7.1 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 18 Aug 2026 - **Updated:** 19 Aug 2026 - **Also known as:** AZL-97004, AZL-97007, BELL-CVE-2026-17106, BIT-docker-cli-2026-17106, CLEANSTART-2026-GV65273, CLEANSTART-2026-MN51569, DEBIAN-CVE-2026-17106, ECHO-7ce4-b04c-827e, GHSA-hfg8-hc9c-6c3h, GO-2026-6253, MINI-23h5-wrf9-pq2f, MINI-27j5-q8pp-qhgc, MINI-2cq6-gwhv-x9fp, MINI-2fx6-r4gg-37c8, MINI-34qx-5j8w-chhp, MINI-3fgg-hm8f-gj56, MINI-49q6-78xj-6g4v, MINI-4q2x-5v24-9wc2, MINI-7cjg-3qc9-qhhh, MINI-865x-qfj3-pf97, MINI-8vg8-j8x5-pm2f, MINI-9344-h28r-m5xp, MINI-9rrc-pjf5-39rg, MINI-cwv7-57r5-wghf, MINI-f2x2-7hxq-p557, MINI-f7xg-mw33-jvwx, MINI-gfgm-r3rm-5q7j, MINI-h4w5-67wv-vvpg, MINI-hp49-j8x6-hmwg, MINI-hr73-3xjg-f4r3, MINI-j562-rjg9-cghg, MINI-j7gx-5pv8-h53w, MINI-jvp2-fqm7-rfrf, MINI-mfw8-rmw4-5x6m, MINI-p3wv-4838-x3xw, MINI-ppvc-59j6-fc42, MINI-r69m-g2mg-8vj4, MINI-rhj5-7mwq-7g9p, MINI-v862-c9rm-rv9m, MINI-vm6g-2hjg-wm9x, MINI-w37f-rgqp-qmmp, MINI-w3g3-j2rf-px7v, MINI-wcrv-7mm3-mf27, MINI-wgpv-mh2g-xm85, MINI-xgh2-g788-qhf2, MINI-xmj5-6gh9-mgh2, OESA-2026-3526, ROOT-APP-GOBINARY-CVE-2026-17106, SUSE-SU-2026:3863-1, UBUNTU-CVE-2026-17106, openSUSE-SU-2026:11544-1, openSUSE-SU-2026:21611-1 ## What is CVE-2026-17106? CVE-2026-17106 is a high-severity path traversal vulnerability in Docker CLI, published on 18 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-59 (Improper Link Resolution Before File Access) ## Which versions are affected by CVE-2026-17106? 4 open source packages ship an affected version, including docker-cli and github.com/moby/go-archive. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `docker-cli` | Bitnami | All versions | 29.7.0 | | `github.com/moby/go-archive` | Go | All versions | 0.3.0 | | `github.com/moby/go-archive` | Go | All versions | 0.3.0 | | `github.com/moby/go-archive` | Go | All versions | 0.3.0 | | `apptainer` | SUSE:Linux Enterprise Module for HPC 15 SP7 | All versions | 1.5.3-150600.4.37.1 | | `apptainer` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 1.5.3-150600.4.37.1 | | `apptainer` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 1.5.3-150600.4.37.1 | | `apptainer` | openSUSE:Leap 16.0 | All versions | 1.5.3-bp160.2.1 | | `apptainer` | openSUSE:Tumbleweed | All versions | 1.5.3-2.1 | ## How do I fix CVE-2026-17106? Upgrade docker-cli to 29.7.0 or later. ## Is CVE-2026-17106 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-17106 exists. Public exploit code: - PoC repository for the blog post CopyEscape: Taking Over Docker Hosts with docker cp (github_poc): https://github.com/masasron/CopyEscape-CVE-2026-17106 - CopyEscape (CVE-2026-17106) docker cp container-to-host arbitrary file write PoC mirror — Imperva Ron Masas, MIT; for authorized security testing (github_poc): https://github.com/HackSpeak/CVE-2026-17106 - PoC funcional de CVE-2026-17106 (CopyEscape): carrera TOCTOU en docker cp que permite escritura arbitraria en el host Docker. Laboratorio Docker + monitor inotify + LD_PRELOAD. Variante macOS inocua y Linux destructiva. (github_poc): https://github.com/686f6c61/POC-CopyEscape-CVE-2026-17106 - Offline Docker CopyEscape evidence checker for CVE-2026-17106. Docker version and build-configuration evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads. (github_poc): https://github.com/CompleteTech-Security/copyescape-check ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-17106 and fix it if it is affected. What it is: CVE-2026-17106 is a high-severity path traversal vulnerability in Docker CLI, published on 18 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-17106 exists. Affected packages and fixed versions: - docker-cli (Bitnami): affected all versions; fixed in 29.7.0 - github.com/moby/go-archive (Go): affected all versions; fixed in 0.3.0 - github.com/moby/go-archive (Go): affected all versions; fixed in 0.3.0 - github.com/moby/go-archive (Go): affected all versions; fixed in 0.3.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-17106/ (Markdown: https://insights.sbomify.com/CVE-2026-17106/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-17106 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-17106 - OSV: https://osv.dev/vulnerability/CVE-2026-17106 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-17106/ Summaries are generated and may contain mistakes; the official description above is the record.