CVE Tools

CVE-2026-17106

Tar extraction in moby/go-archive can write outside the destination directory via link following

No known exploitation. EPSS puts it in the 37th percentile. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • Moby Go-archiveAffected: < 0.3.0Upgrade to: 0.3.0Stated by: CVE record
  • Docker SandboxesAffected: < 0.38.0Upgrade to: 0.38.0Stated by: CVE record
  • Docker DesktopAffected: < 4.86.0Upgrade to: 4.86.0Stated by: CVE record
  • Docker EngineAffected: < 29.7.0Upgrade to: 29.7.0Stated by: CVE record
  • Docker CLIAffected: < 29.7.0Upgrade to: 29.7.0Stated by: CVE record

Versions as the sources state them. 1 more product has version data. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS37th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.4% chance of exploitation activity in the next 30 days, which ranks it in the 37th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

12 events over 10 days, from the signal feeds we watch.

  1. Workaround availablerecord updated
  2. OpenVAS check added
  3. Workaround availablerecord updated
  4. Workaround availableworkaround available, published, weakness classified, att&ck mapped, record updated, record updated

Affected products

Technical detail

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Docker Sandboxes, not every advisory.