CVE-2026-17106GO-2026-6253BIT-DOCKER-CLI-2026-17106GHSA-HFG8-HC9C-6C3H
Tar extraction in moby/go-archive can write outside the destination directory via link following
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.3.0, 0.38.0, 4.86.0, 29.7.0, 5.4.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 4 proofs of concept on GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- CVE published
- Record last updated
Affected versions
- github.com/moby/go-archive
fixed in 0.3.0
- Docker Docker Sandboxes
fixed in 0.38.0
- Docker Docker Desktop
fixed in 4.86.0
- Docker Docker Engine
fixed in 29.7.0
- Docker Docker CLI
fixed in 29.7.0
- Docker Docker Compose
fixed in 5.4.0
- github.com/moby/go-archiveGo
fixed in 0.3.0