Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

CVSS 3.1 7.2 HIGHEUVD CVSS 3.1 7.5 CVSS 3.1 · [email protected] · Secondary 7.2 HIGHCVSS 3.1 · 0b0ca135-0b70-47e7-9f44-1890c2a1c46c · Secondary 7.5 HIGHCVSS_V3 Publisher rating HIGHFixed by github.com/moby/moby/v2 2.0.0-beta.14osv · severity unknownFixed by github.com/moby/moby/v2 2.0.0-beta.14KEV status unknown

cve-program · CVE-2026-41567

Published

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

Read the publisher's advisory

euvd · EUVD-2026-34779

Published

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

Read the publisher's advisory

nvd · CVE-2026-41567

Published

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

Read the publisher's advisory

osv · GHSA-x86f-5xw2-fm2r

Published

## Summary When a user uploads a compressed archive into a container, a malicious image can execute arbitrary code with daemon (host root) privileges. ## Details When handling `PUT /containers/{id}/archive` requests with compressed archives, the daemon decompresses them using external system binaries. Due to incorrect ordering of operations, these binaries are resolved from the container's filesystem rather than the host's. A container image that includes a trojanized decompression binary can achieve code execution as the daemon process whenever a compressed archive is uploaded to that container. The executed binary runs with the daemon's full privileges, including host root UID and unrestricted capabilities. ## Impact Arbitrary code execution as host root, crossing the container-to-host trust boundary. ### Conditions for exploitation - A user must run a container from a malicious image that contains a trojanized decompression binary. - The user must then upload a compressed archive (xz or gzip) into that container, either by piping a compressed archive via `docker cp -` or by calling the `PUT /containers/{id}/archive` API directly with compressed content. ### Not affected Standard `docker cp` usage is **not** affected, because the CLI sends uncompressed tar by default: ``` docker cp ./file.txt mycontainer:/file.txt ``` This can only be exploited when explicitly passing a xz or gzip-compressed archive to `docker cp` or the `PUT /containers/{id}/archive` API, for example: ``` cat archive.tar.xz | docker cp - mycontainer:/dir ``` Decompression formats using pure Go implementations (bzip2, zstd, and gzip when the container image does not contain an `unpigz` binary) are also not affected. ## Workarounds - Only run containers from trusted images. - Use authorization plugins to limit access to the `PUT /containers/{id}/archive` endpoint. - Avoid piping compressed archives into containers created from untrusted images.

Read the publisher's advisory

osv · GO-2026-5746

Published

The Docker daemon's implementation of the "PUT /containers/{id}/archive" endpoint executes a container binary on the host when extracting an archive to a container. On Unix-like systems, this can be exploited if an attacker can control the container's filesystem or the archive being extracted, potentially leading to privilege escalation or host compromise. The affected code is located in the daemon package, specifically in the containerExtractToDir method of the Daemon struct. This package is part of the Moby daemon's core and is not intended for external use as a library.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-41567

Published

moby/v2/daemon

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "moby",
                    "product": "moby/v2/daemon",
                    "versions": [
                        {
                            "version": "< 2.0.0-beta.14",
                            "status": "affected"
                        }
                    ]
                }

Docker Engine

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "moby",
                    "product": "Docker Engine",
                    "versions": [
                        {
                            "version": "< 29.5.1",
                            "status": "affected"
                        }
                    ]
                }

docker/daemon

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "docker",
                    "product": "docker/daemon",
                    "versions": [
                        {
                            "version": "<= 28.5.2",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-34779

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jun 5, 2026, 12:35:50 AM

dateUpdated: Sep 9, 2026, 12:04:44 PM

21 related source bulletins · separate from aliases

WID-SEC-W-2026-1584: docker: Mehrere Schwachstellen

CVE-2026-41567 · CVE-2026-41568 · CVE-2026-42306

openSUSE-SU-2026:21205-1: Security update for docker-stable

CVE-2026-33186 · CVE-2026-33814 · CVE-2026-33997 · CVE-2026-34040 · CVE-2026-39821 · CVE-2026-41567

SUSE-SU-2026:22456-1: Security update for docker

CVE-2026-33814 · CVE-2026-39821 · CVE-2026-39984 · CVE-2026-41567

SUSE-SU-2026:22285-1: Security update for docker

CVE-2026-33814 · CVE-2026-39821 · CVE-2026-39984 · CVE-2026-41567

SUSE-SU-2026:24318-1: Security update for docker

CVE-2026-33814 · CVE-2026-39821 · CVE-2026-39984 · CVE-2026-41567

openSUSE-SU-2026:21060-1: Security update for docker

CVE-2026-33814 · CVE-2026-39821 · CVE-2026-39984 · CVE-2026-41567

RHSA-2026:44622: Red Hat Security Advisory: Multicluster Global Hub 1.6.4 security update

CVE-2026-25681 · CVE-2026-27136 · CVE-2026-27145 · CVE-2026-33376 · CVE-2026-33377 · CVE-2026-33811 · CVE-2026-39821 · CVE-2026-41567 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-43870 · CVE-2026-46384 · CVE-2026-46385 · CVE-2026-53488 · CVE-2026-53492 · CVE-2026-55677

SUSE-SU-2026:24410-1: Security update for docker

CVE-2026-31431 · CVE-2026-33814 · CVE-2026-39821 · CVE-2026-39984 · CVE-2026-41567

SUSE-SU-2026:22513-1: Security update for docker

CVE-2026-33814 · CVE-2026-39821 · CVE-2026-39984 · CVE-2026-41567

openSUSE-SU-2026:11075-1: docker-stable-24.0.9_ce-18.1 on GA media

CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33814 · CVE-2026-33997 · CVE-2026-34040 · CVE-2026-39821 · CVE-2026-41567

openSUSE-SU-2026:11144-1: docker-29.4.0_ce-40.1 on GA media

CVE-2026-33814 · CVE-2026-39821 · CVE-2026-39984 · CVE-2026-41567

RHSA-2026:51057: Red Hat Security Advisory: OpenShift Source To Image 1.6.3

CVE-2026-27145 · CVE-2026-33811 · CVE-2026-41567 · CVE-2026-42306 · CVE-2026-42504

RHSA-2026:42852: Red Hat Security Advisory: Multicluster Global Hub 1.5.6 security update

CVE-2026-25681 · CVE-2026-27136 · CVE-2026-33376 · CVE-2026-33377 · CVE-2026-33811 · CVE-2026-39821 · CVE-2026-41567 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-43870 · CVE-2026-46384 · CVE-2026-46385 · CVE-2026-53488 · CVE-2026-53492

RHSA-2026:41030: Red Hat Security Advisory: Multicluster Global Hub 1.4.7 security update

CVE-2026-25681 · CVE-2026-27136 · CVE-2026-27145 · CVE-2026-33811 · CVE-2026-39821 · CVE-2026-41567 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-43870 · CVE-2026-46384 · CVE-2026-46385 · CVE-2026-53488 · CVE-2026-53492

SUSE-SU-2026:22367-1: Security update for docker

CVE-2026-33814 · CVE-2026-39821 · CVE-2026-39984 · CVE-2026-41567

RHSA-2026:97562: Red Hat Security Advisory: skopeo security, bug fix, and enhancement update

CVE-2026-33811 · CVE-2026-41567

openSUSE-SU-2026:22158-1: Security update for docker

CVE-2026-31431 · CVE-2026-33814 · CVE-2026-39821 · CVE-2026-39984 · CVE-2026-41567

SUSE-SU-2026:4533-1: Security update for docker-stable

CVE-2026-33186 · CVE-2026-33814 · CVE-2026-39821 · CVE-2026-41567

RHSA-2026:97229: Red Hat Security Advisory: skopeo security, bug fix, and enhancement update

CVE-2026-41567

RHSA-2026:37387: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.22.0 security, enhancement & bug fix update

CVE-2024-25621 · CVE-2024-40635 · CVE-2024-45310 · CVE-2025-8766 · CVE-2025-21613 · CVE-2025-21614 · CVE-2025-22870 · CVE-2025-47911 · CVE-2025-52881 · CVE-2025-54410 · CVE-2025-58058 · CVE-2025-64329 · CVE-2025-66506 · CVE-2026-22772 · CVE-2026-23831 · CVE-2026-24117 · CVE-2026-25680 · CVE-2026-25681 · CVE-2026-25934 · CVE-2026-27136 · CVE-2026-27141 · CVE-2026-27903 · CVE-2026-33540 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-35172 · CVE-2026-35469 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-39883 · CVE-2026-41506 · CVE-2026-41567 · CVE-2026-41568 · CVE-2026-42502 · CVE-2026-42506 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-45571 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598

SUSE-SU-2026:24279-1: Security update for docker

CVE-2026-31431 · CVE-2026-33814 · CVE-2026-39821 · CVE-2026-39984 · CVE-2026-41567

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-41567

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Awaiting Analysis

Weakness classifications: CWE-427

Original publisher date fields

published: 2026-06-05T02:17:13.817

lastModified: 2026-09-09T13:19:53.313

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-x86f-5xw2-fm2r

Published

github.com/moby/moby/v2

Go

SEMVER · introduced 0 → fixed 2.0.0-beta.14

github.com/docker/docker

Go

SEMVER · introduced 0 → last_affected 28.5.2

github.com/moby/moby

Go

SEMVER · introduced 0 → last_affected 28.5.2

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2026-5746

Published

github.com/docker/docker

Go

SEMVER · introduced 0

github.com/moby/moby

Go

SEMVER · introduced 0

github.com/moby/moby/v2

Go

SEMVER · introduced 0 → fixed 2.0.0-beta.14

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 06:51 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current