HighCVE-2026-17106

    Tar extraction in moby/go-archive can write outside the destination directory via link following (CVE-2026-17106)

    Published Last modified Sources: Red Hat, BSI, OSV, SUSE, CVE.org, Hersteller, Msrc Update Guide

    What is affected, what to do

    A flaw was found in moby/go-archive. The tar extraction routines in the component do not properly restrict filesystem operations to the intended destination directory.

    An exploit is publicly available. Update Moby Go-archive to version 0.3.0, Docker Sandboxes to version 0.38.0, Docker Desktop to version 4.86.0.

    Affected
    • Moby Go-archive lt *..0.3.0
    • Docker Sandboxes lt *..0.38.0
    • Docker Desktop lt *..4.86.0
    • Docker Engine lt *..29.7.0
    • Docker CLI lt *..29.7.0
    • Docker Compose lt *..5.4.0
    Fixed in
    • Moby Go-archive 0.3.0
    • Docker Sandboxes 0.38.0
    • Docker Desktop 4.86.0
    • Docker Engine 29.7.0
    • Docker CLI 29.7.0
    • Docker Compose 5.4.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.1

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v4

    7.1

    CVSS v4

    Severity High on the scale from 0 to 10.

    Source: Red Hat, BSI, OSV, SUSE, CVE.org, Hersteller, Msrc Update Guide

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 38.0

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    70.88 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    PoC (publicly reported)
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.1 Methodology
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.1
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.4 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    38.0
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-59

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    A flaw was found in moby/go-archive. The tar extraction routines in the component do not properly restrict filesystem operations to the intended destination directory. An attacker who controls the contents of an archive can exploit this by including symbolic links, allowing them to create or overwrite files at arbitrary locations on the system where the archive is being extracted. This could lead to unauthorized modification of system files or potentially arbitrary code execution.

    Source: redhat_csaf, BSI WID Portal, BSI CSAF, OSV (Open Source Vulnerabilities), suse_csaf, NVD (NIST), cvelistv5, GitHub Security Advisories, Microsoft Security Update Guide

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    DockerDocker CLI
    • < 29.7.0
    • 29.7.0
    DockerDocker Compose
    • < 5.4.0
    • 5.4.0
    DockerDocker Desktop
    • < 4.86.0
    • 4.86.0
    DockerDocker Engine
    • < 29.7.0
    • 29.7.0
    DockerDocker Sandboxes
    • < 0.38.0
    • 0.38.0
    mobygo-archive
    • < 0.3.0
    • 0.3.0
    Open Sourcedocker
    • < 29.7.0
    • 29.7.0
    gogithub.com/moby/go-archive
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-59Improper Link Resolution Before File Access ('Link Following')

      Base

      The product 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.

      Entry at MITRE CWE-59

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    PoC-in-GitHub (nomi-sec)POC-CopyEscape-CVE-2026-17106 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-17106 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CopyEscape-CVE-2026-17106 (opens in a new tab)github.comPoC (publicly reported)reported, not verified

    References & sources

    • github.commoby/go-archive/security/advisories/GHSA-hfg8-hc9c-6c3hVendor advisory
    • docs.docker.comdesktop/release-notesRelease notes
    • github.comdocker/sbx-releases/releases/tag/v0.38.0Release notes
    • docs.docker.comengine/release-notes/29Release notes
    • github.comdocker/cli/releases/tag/v29.7.0Release notes
    • github.comdocker/compose/releases/tag/v5.4.0Release notes
    • github.commoby/go-archive/releases/tag/v0.3.0Patch
    • github.commasasron/CopyEscape-CVE-2026-17106Exploit
    • github.commoby/moby/issues/52948web
    • github.combikini/exploitarium/tree/main/docker-cp-copyout-destination-esc…web
    • github.commoby/go-archivepackage
    • github.commoby/moby/releases/tag/docker-v29.7.0web
    • imperva.comblog/copyescape-taking-over-docker-hosts-with-docker-cpweb
    • NVD (NIST)vuln/detail/CVE-2026-17106web

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: proof of concept, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentchanged
      {"id":"CVE-2026-17106","role":"CISA Coordinator","options":[{"exploitation":"poc"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-18T18:50:49.774785Z"}
      {"id":"CVE-2026-17106","role":"CISA Coordinator","options":[{"exploitation":"poc"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-18T00:00:00+00:00"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-17106
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-17106"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-17106.svg?lang=en" alt="CVE-2026-17106 – NEOSEC Intel" height="20"></a>