Docker: `PUT /containers/{id}/archive` executes container binary on the host

Summary

Moby is an open source container framework. In versions prior to 29.5.1 and in moby/moby v2 prior to v2.0.0-beta.14, when a compressed archive is uploaded to a container via `PUT /containers/{id}/archive` or piped through `docker cp -`, the daemon resolves decompression binaries (such as `xz` or `unpigz`) from the container's filesystem rather than the host's due to incorrect ordering of operations. A malicious container image containing a trojanized decompression binary can achieve arbitrary code execution with full daemon privileges, including host root UID and unrestricted capabilities, when a user uploads a compressed (xz or gzip) archive into that container. This issue is fixed in Docker Engine 29.5.1 and moby/moby v2.0.0-beta.14. Workarounds include only running containers from trusted images, using authorization plugins to restrict access to the `PUT /containers/{id}/archive` endpoint, and avoiding piping compressed archives into containers created from untrusted images

Timeline

1. Jun 5, 2026, 12:35 AM UTCCVE published
2. Jun 5, 2026, 1:11 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Sep 9, 2026, 12:04 PM UTCRecord last updated

Affected versions

• moby moby/v2/daemon

  fixed in 2.0.0-beta.14

• moby Docker Engine

  fixed in 29.5.1

• docker docker/daemon

  through 28.5.2

• github.com/moby/moby/v2Go

  fixed in 2.0.0-beta.14

• github.com/docker/dockerGo

  through 28.5.2

• github.com/moby/mobyGo

  through 28.5.2

• github.com/docker/dockerGo

  All versions

• github.com/moby/mobyGo

  All versions

References 2