Skip to main content
Report · Reddit CybersecurityAbout CVE-2026-17106Published

CVE-2026-17106: CopyEscape · Container-to-host arbitrary file write via docker cp

Source Reddit Cybersecurity

0
Compare
Authoritative record:CVE-2026-17106· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 0.3.0 soon.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.3.0, 0.38.0, 4.86.0 +2
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CISA SSVC: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Docker Inc.

    , 25 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    proof of concept public

    , the same day as disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
mobygo-archiveAffected
  • <0.3.0
Fixed in
  • 0.3.0
DockerDocker SandboxesAffected
  • <0.38.0
Fixed in
  • 0.38.0
DockerDocker DesktopAffected
  • <4.86.0
Fixed in
  • 4.86.0
DockerDocker EngineAffected
  • <29.7.0
Fixed in
  • 29.7.0
DockerDocker CLIAffected
  • <29.7.0
Fixed in
  • 29.7.0
DockerDocker ComposeAffected
  • <5.4.0
Fixed in
  • 5.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Docker has released official fixes for this vulnerability in Docker Engine/CLI version 29.7.2 and later, Docker Desktop 4.86.0 and later, and Docker Sandboxes 0.38.0 and later. Users should upgrade to these versions or later to mitigate the risk. No additional vendor advisories indicate other mitigation steps or that no action is required.

Discussion

CVE-2026-17106, known as CopyEscape, is a high-severity vulnerability in Docker's 'docker cp' command that allows a malicious container to write arbitrary files to the host filesystem. The flaw stems from a filesystem race condition during archive creation combined with unsafe symbolic link handling during extraction. This can lead to arbitrary file creation or overwriting on the host and potentially code execution depending on the privileges of the Docker CLI user. Docker has released official fixes in Docker Engine/CLI version 29.7.2 and later, Docker Desktop 4.86.0 and later, and Docker Sandboxes 0.38.0 and later.

r/cybersecurity (opens in a new tab)u/ronmasas0 points0 comments

https://www.imperva.com/blog/copyescape-taking-over-docker-hosts-with-docker-cp/

Author here. I discovered a vulnerability in docker cp that allows a malicious container to create or overwrite files on the machine running the Docker CLI.

The exploit combines a filesystem race in Docker’s archive creation with unsafe symlink handling during extraction. Depending on the CLI user’s privileges, this can lead to code execution. Docker confirmed that sbx cp was also affected.

Fixed versions:

  • Docker Engine/CLI 29.7.2+
  • Docker Desktop 4.86.0+
  • Docker Sandboxes 0.38.0+

Happy to answer technical questions.

References

Community reviews

Loading reviews…