CVE 7.2 HIGH

Docker: `PUT /containers/{id}/archive` executes container binary on the host_CVE-2026-41567

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

Description

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

Basic Information

ID CVE-2026-41567
Source GitHub_M
Published Jun 5, 2026 at 00:35

Affected Product

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

CWE Classification

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.