CVE-2026-17106: Tar extraction in moby/go-archive can write outside the destination directory via link following
moby · go-archive
Vendor fix available · Affected: moby go-archive · Exploitation: public proof of concept (unverified)
ExploitationProof of concept public
Not in CISA KEV as of catalogue 2026.11.17 (17 Nov)
- In CISA KEV: not seen
- Exploited (reported): not seen
- Scanning observed: not seen
- Proof of concept public4 public GitHub repositories (unverified), listed by PoC-in-GitHub9 Aug
- Not established: not seen
Higher than 38% of scored CVEs
DescriptionNVD
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.
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- moby
- Published
- August 2026
What changed
- PoC-in-GitHub lists 4 public GitHub repositories (unverified) PoC-in-GitHub
Coverage1 article · 1 outlet
First in our coverage: SecurityOnline, 17 Aug.
- Docker CopyEscape bug lets attackers write files via docker cpSecurityOnline · first in our coverage
New articles also arrive in the RSS feed.