CVE-2026-17106: moby go-archive · Link Following
Affects moby go-archiveSource CVE Database V5
Public exploit available · CVSS 7.1 High : upgrade to 0.3.0 as a priority.
Data as of 26 Oct 2026, 11:07 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- Proof of concept is public or traded
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-08-18.
- Patch
- Available – fixed in 0.3.0, 0.38.0, 4.86.0 +2
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CISA SSVC: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by Docker Inc.
, 25 days before disclosure
CVE published
on cve.org
, t = 0
CISA SSVC assessment
proof of concept public
, the same day as disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mobygo-archive | Affected
| Fixed in
|
| DockerDocker Sandboxes | Affected
| Fixed in
|
| DockerDocker Desktop | Affected
| Fixed in
|
| DockerDocker Engine | Affected
| Fixed in
|
| DockerDocker CLI | Affected
| Fixed in
|
| DockerDocker Compose | Affected
| Fixed in
|
CPE configurations (2)
cpe:2.3:a:docker:docker_sandboxes:*:*:*:*:*:*:*:*cpe:2.3:a:docker:desktop:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
Reports on CVE-2026-17106
References
- github.com/moby/go-archive/security/advisories/GHSA-hfg8-hc9c-6c3h (opens in a new tab)
- docs.docker.com/desktop/release-notes/ (opens in a new tab)
- github.com/docker/sbx-releases/releases/tag/v0.38.0 (opens in a new tab)
- docs.docker.com/engine/release-notes/29/ (opens in a new tab)
- github.com/docker/cli/releases/tag/v29.7.0 (opens in a new tab)
- github.com/docker/compose/releases/tag/v5.4.0 (opens in a new tab)
- github.com/moby/go-archive/releases/tag/v0.3.0 (opens in a new tab)
- github.com/masasron/CopyEscape-CVE-2026-17106 (opens in a new tab)