moby · Docker Engine (Moby) · published 2026-06-05

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

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-41567 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 25% of all CVEs. This Docker Engine (Moby) vulnerability: CVSS 7.2 (v3.1), a successful attack gives total control of the component. Fixed upstream in Docker Engine (Moby) 29.5.1. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Docker Engine (Moby) 29.5.1.

Patch events

  1. This monthSecurity release

    Container runtimeDocker Engine (Moby)

    Docker Engine (Moby) security release: 29.5.1

    Upgrade to 29.5.1

    Why: Vendor security release for server software (most severe: CVE-2026-41567).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (25th pct)FIRST EPSS v2026.06.15
CVSS base score7.2 (v3.1)
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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 from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →