CVE-2026-17106

Published: Ago 18, 2026 Last Modified: Ago 18, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 7,1
Attack Vector: local
Attack Complexity: low
Privileges Required: none
User Interaction: active
Confidentiality: N/A
Integrity: N/A
Availability: N/A

Description

AI Translation Available

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.

59

Improper Link Resolution Before File Access ('Link Following')

Draft
Common Consequences
Security Scopes Affected:
Confidentiality Integrity Access Control Other
Potential Impacts:
Read Files Or Directories Modify Files Or Directories Bypass Protection Mechanism Execute Unauthorized Code Or Commands
Applicable Platforms
Operating Systems: Windows, Unix
View CWE Details
https://github.com/masasron/CopyEscape-CVE-2026-17106
https://docs.docker.com/desktop/release-notes/#4860
https://docs.docker.com/engine/release-notes/29/#2970
https://github.com/docker/cli/releases/tag/v29.7.0
https://github.com/docker/compose/releases/tag/v5.4.0
https://github.com/docker/sbx-releases/releases/tag/v0.38.0
https://github.com/moby/go-archive/releases/tag/v0.3.0
https://github.com/moby/go-archive/security/advisories/GHSA-hfg8-hc9c-6c3h