Loading story…
Imperva disclosed CopyEscape, tracked as CVE-2026-17106, a container-to-host arbitrary file-write vulnerability in Docker’s docker cp functionality that allows a malicious container to create or overwrite files outside the destination chosen by the user on the machine running the Docker CLI. The issue stems from a filesystem race in Docker’s archive creation path combined with unsafe symlink handling during extraction, turning a routine file copy from a container into a host write primitive.
Docker confirmed the same CVE also affects sbx cp in Docker Sandboxes when copying files out of sandboxes. Imperva said exploitation was validated against Docker Engine 29.6.1 on Linux and Docker Desktop 4.81.0 on macOS, with impact ranging from compromise of the developer account using the CLI to root code execution when docker cp is run with elevated privileges. Fixes are available in Docker Engine and CLI 29.7.2 or later, Docker Desktop 4.86.0 or later, and Docker Sandboxes 0.38.0 or later.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
5 events from the most recent confirmed update back to the earliest known activity.
Docker released Docker Desktop 4.86.0 with Docker Engine 29.7.2 to address CVE-2026-17106. These versions were identified as the fixed releases for the vulnerable `docker cp` behavior.
Docker Sandboxes 0.38.0 shipped a fix for the related destination-escape flaw in `sbx cp` copy-out under CVE-2026-17106. Docker had confirmed the same CVE also affected copying files out of Docker Sandboxes.
On July 14, 2026, Docker said it was pursuing two remediation tracks for CVE-2026-17106: hardening the extraction library as the primary fix and hardening the source filesystem walk as defense in depth. The reference also notes follow-up fixes were needed after initial hardening caused significant functional regressions.
Imperva reported the container-to-host arbitrary file-write vulnerability CVE-2026-17106 in Docker's `docker cp` functionality to Docker. The flaw could let a malicious container overwrite files outside the user-selected destination on the machine running the Docker CLI.
A public proof-of-concept exploit became available for CVE-2026-17106, increasing the risk of exploitation of the Docker `docker cp`/`sbx cp` flaw. The reference notes Docker had already patched the issue and recommends updating Docker Desktop to 4.86.0 or later.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
4 references tracked. Mallory keeps watching after this page renders.
acn.gov.it
Open sourcethecybersecguru.com
Open sourcereddit.com
Open sourceimperva.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Docker disclosed a high-severity Docker Engine vulnerability, **CVE-2026-34040** (`CVSS 8.8`), that allows attackers to bypass authorization plugins and perform actions that should be blocked. The flaw stems from an incomplete fix for **CVE-2024-41110** and is triggered when a specially crafted oversized Docker API request causes the request body to be dropped before inspection by an AuthZ plugin. In affected environments, the plugin may approve container operations it would otherwise deny, opening a path to unauthorized privileged actions and potential host compromise. Researchers said an attacker with Docker API access could exploit the bug by padding a container-creation request beyond **1 MB** to launch a privileged container with access to the host filesystem, exposing sensitive assets such as **AWS credentials**, **SSH keys**, and **Kubernetes configurations**. The issue affects deployments that rely on authorization plugins inspecting request bodies, while environments not using those plugins are not impacted. Docker patched the vulnerability in **Docker Engine 29.3.1** and urged defenders to upgrade, restrict Docker API access, avoid AuthZ plugins that depend on request-body inspection, and use controls such as rootless mode, user namespace remapping, and least-privilege access to reduce risk.
Jul 23, 2026
Security researchers have disclosed three critical vulnerabilities in the runC container runtime, which is widely used in platforms such as Docker and Kubernetes. The flaws, identified as CVE-2025-31133, CVE-2025-52565, and CVE-2025-52881, arise from logic and race-condition errors in runC's handling of temporary bind mounts, symbolic links, and certain write operations. Attackers can exploit these weaknesses to break container isolation, potentially gaining write access to sensitive host system files and kernel interfaces such as `/proc/sys/kernel/core_pattern` or `/proc/sysrq-trigger`, leading to full container escapes and even host-level compromise. The vulnerabilities allow attackers to abuse masked paths, console bind-mounts, and redirected writes, bypassing standard hardening and isolation controls. Exploitation requires either custom mount configurations or the use of untrusted container images, but the risk is significant for orchestrated environments like Docker and Kubernetes. Security advisories from both the runC project and the U.S. National Vulnerability Database urge immediate updates to patched versions or the application of provided patches to mitigate these threats. The vulnerabilities highlight the importance of robust container runtime security and the potential impact of logic flaws in core infrastructure components.
Jun 29, 2026
Docker released security updates for **CVE-2024-41110**, a critical flaw in Docker Engine that can let attackers bypass authorization controls and potentially escalate privileges when **AuthZ authorization plugins** are enabled. The bug is a regression of an issue first addressed in 2019, but the earlier fix was not carried forward into newer Docker Engine releases starting with `19.03`, leaving later versions exposed. Docker Desktop installations are also affected through the bundled engine. The vulnerability can be exploited by sending a specially crafted Docker API request with `Content-Length: 0`, causing the daemon to pass the request to authorization plugins **without the request body** and potentially leading to incorrect allow decisions and command execution. Affected versions include Docker Engine before `23.0.14` and before `27.1.0`, and Docker Desktop before `4.33`; Mirantis Container Runtime and deployments not using AuthZ plugins are not impacted. Defenders were urged to update immediately or, if patching is not yet possible, disable AuthZ plugins and restrict Docker API access to trusted users and systems.
Jul 24, 2026