LiveActive security incident?Get immediate response
CVE Record

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

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

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Docker Engine has a flaw where copying a compressed file into a container can accidentally run a malicious program supplied by that container, giving it full control of the host machine. The risk shows up when someone uses `docker cp` or the archive upload API against a container built from an untrusted image. Docker Engine 29.5.1 and moby/moby v2.0.0-beta.14 fix the issue.

Executive priority

Treat as a high-priority patch cycle for any team running Docker on shared build infrastructure or with third-party images. No known active exploitation, but a successful attack yields host root, so schedule the upgrade in the next standard maintenance window and tighten image-trust policy in parallel.

Technical view

When the daemon handles `PUT /containers/{id}/archive` (or `docker cp -`), it resolves decompression helpers such as `xz` or `unpigz` from the container's own filesystem before the host's, an untrusted search path (CWE-427). A trojanized binary inside the image therefore executes as the daemon: host root UID with unrestricted capabilities. Trigger requires local daemon access, a compressed upload, and user interaction against a hostile image.

Likely exposure

Any host running Docker Engine ≤28.5.2, ≤29.5.0, or moby/moby v2 prior to v2.0.0-beta.14 is exposed if operators ever copy compressed archives into containers built from untrusted or third-party images. CI/CD runners, shared build hosts, and multi-tenant Docker environments are the highest-risk footprints.

Exploitation context

Not listed in CISA KEV and no public in-the-wild exploitation is cited in the bundle. CVSS 7.5 with AV:L/AC:H/PR:L/UI:R reflects a local, user-interaction-dependent path. The scenario is realistic for supply-chain style abuse of public images but requires a victim to copy a compressed file into the malicious container.

Researcher notes

Root cause is an untrusted search path (CWE-427): the daemon consults the container rootfs for decompression helpers before the host, letting a hostile image win the lookup. Scope is Changed and impact is C:H/I:H/A:H because the process breaks out to the host with full daemon privileges. Focus validation on Engine build strings and on any custom code paths that wrap `docker cp`.

Mitigation direction

  • Upgrade Docker Engine to 29.5.1 or later, or moby/moby v2 to v2.0.0-beta.14 or later.
  • Apply the vendor package update tracked by RHSA-2026:37387 on Red Hat hosts.
  • Restrict container images to trusted, signed sources and internal registries.
  • Deploy an authorization plugin that blocks or scopes `PUT /containers/{id}/archive`.
  • Avoid piping compressed archives into containers created from untrusted images.
  • Audit CI/CD and developer workflows that call `docker cp` against third-party images.

Validation and detection

  • Run `docker version` on every host and confirm the Engine build is 29.5.1 or newer.
  • Inventory moby/moby v2 deployments and verify the release is v2.0.0-beta.14 or later.
  • Check Red Hat systems for the RHSA-2026:37387 errata being installed.
  • Review authorization plugin policy to confirm archive-upload endpoints are gated.
  • Search image registries and pipelines for untrusted sources that could ship trojanized xz/unpigz.
  • Consult the moby GHSA-x86f-5xw2-fm2r advisory for any updated guidance.
Prepared
Confidence
high
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-427: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-41567 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H0.86redhat-SADP
7.2CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N0.85.8GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-41567Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPdocker: Moby/Docker Engine: Arbitrary Code Execution via malicious container image and compressed archive upload
other:Red Hat severity ratingcvssV3_1
  • 2026-06-05T02:00:54.488Z: Reported to Red Hat.
  • 2026-06-05T00:35:50.563Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
mobymoby/v2/daemon< 2.0.0-beta.14Listed
mobyDocker Engine< 29.5.1Listed
dockerdocker/daemon<= 28.5.2Listed
Weakness

CWE details

CWE-427

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-427 · source CWE mapping

Uncontrolled Search Path Element

Uncontrolled Search Path Element represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs