CVE-2026-41567 PUBLISHED

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

Assigner: GitHub_M
Reserved: 21.04.2026 Published: 05.06.2026 Updated: 05.06.2026

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

Metrics

CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N
CVSS Score: 7.2

Product Status

Vendor moby
Product moby/v2/daemon
Versions
  • Version < 2.0.0-beta.14 is affected
Vendor moby
Product Docker Engine
Versions
  • Version < 29.5.1 is affected
Vendor docker
Product docker/daemon
Versions
  • Version <= 28.5.2 is affected

References

Problem Types

  • CWE-427: Uncontrolled Search Path Element CWE