vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2026-17106

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

HIGH
7.1
CVSS Score
Published: August 18, 2026 at 06:35 PM UTC
Updated: August 28, 2026 at 03:42 PM UTC
7 products affected across 2 vendorsDesktopDockerDocker Desktop

Using go-archive by moby?

Get instant alerts when new vulnerabilities affect go-archive - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
HIGH7.1
Exploit prediction
EPSS 0.4%
SSVC
PoC

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Desktop· Docker
95%
All versions
Command Line Interface· Docker
60%
v < 29.7.0
Affected range stops below 29.7.0, so it looks safe — our inference, not a vendor statement
Docker Compose· Docker
60%
v < 5.4.0
Affected range stops below 5.4.0, so it looks safe — our inference, not a vendor statement
Docker· Docker
60%
v < 29.7.0
Affected range stops below 29.7.0, so it looks safe — our inference, not a vendor statement
Docker Desktop· Docker
60%
v < 4.86.0
Affected range stops below 4.86.0, so it looks safe — our inference, not a vendor statement
Docker Sandboxes· Docker
60%
v < 0.38.0
Affected range stops below 0.38.0, so it looks safe — our inference, not a vendor statement
Go Archive· Moby
60%
v < 0.3.0
Affected range stops below 0.3.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (8)

Vendor Advisory
Source: cverecord
https://github.com/moby/go-archive/security/advisories/GHSA-hfg8-hc9c-6c3h
Release Notes
Source: cverecord
https://docs.docker.com/desktop/release-notes/#4860
Release Notes
Source: cverecord
https://github.com/docker/sbx-releases/releases/tag/v0.38.0
Release Notes
Source: cverecord
https://docs.docker.com/engine/release-notes/29/#2970
Release Notes
Source: cverecord
https://github.com/docker/cli/releases/tag/v29.7.0
Release Notes
Source: cverecord
https://github.com/docker/compose/releases/tag/v5.4.0
Patch
Source: cverecord
https://github.com/moby/go-archive/releases/tag/v0.3.0
Source: 134c704f-9b21-4f2e-91b3-4a467353bcc0
https://github.com/masasron/CopyEscape-CVE-2026-17106

SSVC — Action Prioritization

SSVCPoCNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.1HIGHDocker
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-59

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card