Docker go-archive Untrusted Extraction Enables Arbitrary File Overwrite (CVE-2026-17106)
CVE-2026-17106 Published on August 18, 2026

Tar extraction in moby/go-archive can write outside the destination directory via link following
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.

Vendor Advisory NVD

Vulnerability Analysis

CVE-2026-17106 is exploitable with local system access. This vulnerability is considered to have a low attack complexity. Public availability of a proof of concept (POC) exploit exists for CVE-2026-17106. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity and availability.

Attack Vector:
LOCAL
Attack Complexity:
LOW
Privileges Required:
NONE
User Interaction:
ACTIVE

Weakness Type

What is an insecure temporary file Vulnerability?

The software attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

CVE-2026-17106 has been classified to as an insecure temporary file vulnerability or weakness.


Products Associated with CVE-2026-17106

stack.watch emails you whenever new vulnerabilities are published in Docker Sandboxes or Docker Desktop. Just hit a watch button to start following.

 
 

Affected Versions

moby go-archive: Docker Sandboxes: Docker Desktop: Docker Engine: Docker CLI: Docker Compose: