Skip to main content
VulnerabilityPublished

CVE-2026-17106: moby go-archive · Link Following

Affects moby go-archiveSource CVE Database V5

0

Public exploit available · CVSS 7.1 High : upgrade to 0.3.0 as a priority.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CISA SSVC: proof of concept public

  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

Timeline

  1. CVE ID reserved

    by Docker Inc.

    , 25 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. 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

ProductAffectedFixed in
mobygo-archiveAffected
  • <0.3.0
Fixed in
  • 0.3.0
DockerDocker SandboxesAffected
  • <0.38.0
Fixed in
  • 0.38.0
DockerDocker DesktopAffected
  • <4.86.0
Fixed in
  • 4.86.0
DockerDocker EngineAffected
  • <29.7.0
Fixed in
  • 29.7.0
DockerDocker CLIAffected
  • <29.7.0
Fixed in
  • 29.7.0
DockerDocker ComposeAffected
  • <5.4.0
Fixed in
  • 5.4.0

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

Community reviews

Loading reviews…