Answer in brief
CVE-2026-41567 records a High severity (CVSS 7.2) vulnerability in Docker: `PUT /containers/{id}/archive` executes container binary on the host. The current sources do not mark it as known exploited. The current feed maps docker/docker/daemon (generic), moby/Docker Engine (generic), moby/moby/v2/daemon (generic), github.com/docker/docker (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps docker/docker/daemon (generic), moby/Docker Engine (generic), moby/moby/v2/daemon (generic), github.com/docker/docker (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| docker/docker/daemongeneric | <= 28.5.2 | Not reported |
| moby/Docker Enginegeneric | < 29.5.1 | Not reported |
| moby/moby/v2/daemongeneric | < 2.0.0-beta.14 | Not reported |
| github.com/docker/dockergo | <=28.5.2 | Not reported |
| github.com/docker/dockergo | >=0 | Not reported |
| github.com/moby/mobygo | <=28.5.2 | Not reported |
| github.com/moby/mobygo | >=0 | Not reported |
| github.com/moby/moby/v2go | <2.0.0-beta.14 | 2.0.0-beta.14 |
| github.com/moby/moby/v2go | >=0 <2.0.0-beta.14 | 2.0.0-beta.14 |
Published upstream
Jun 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 11, 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
Quoted source text, attributed separately from HOL analysis.