CVE-2026-17106Public exploit

Arbitrary file overwrite via link following

Published Aug 18, 2026 · Updated Aug 19, 2026

Path traversal in moby/go-archive before 0.3.0 allows attackers to overwrite writable files via a crafted tar archive. Unpack, UnpackLayer, Untar, UntarUncompressed, and ApplyLayer keep entries under the destination with lexical path checks, but the later filesystem operation lets the OS resolve archive-created links, so writes can escape the extraction root. In Docker products, reachability typically requires a local copy-out such as docker cp or sbx cp against attacker-controlled container content; the result is arbitrary file creation or overwrite as the extracting user, which can become host code execution if a sensitive executable or configuration file is replaced.

CVSS severity7.1
High
EPSS probability0.33%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Path traversal in moby/go-archive before 0.3.0 allows attackers to overwrite writable files via a crafted tar archive. Unpack, UnpackLayer, Untar, UntarUncompressed, and ApplyLayer keep entries under the destination with lexical path checks, but the later filesystem operation lets the OS resolve archive-created links, so writes can escape the extraction root. In Docker products, reachability typically requires a local copy-out such as docker cp or sbx cp against attacker-controlled container content; the result is arbitrary file creation or overwrite as the extracting user, which can become host code execution if a sensitive executable or configuration file is replaced.

The record

CVE
CVE-2026-17106
Published
Aug 18, 2026
Updated
Aug 19, 2026
Vendor
Moby Project
Product
go-archive
Classifications
CWE-59, CWE-22
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Aug 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <0.3.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

Moby Project · go-archiveversion=0 <0.3.0
Docker · Docker Desktopversion=0 <4.86.0
Docker · Docker Sandboxesversion=0 <0.38.0
Docker · Docker Engineversion=0 <29.7.0
Docker · Docker CLIversion=0 <29.7.0
Docker · Docker Composeversion=0 <5.4.0

Published CVSS scores

7.1GitHub Advisory DatabaseCVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-59Improper Link Resolution Before File Access ('Link Following')
CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo