Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.2

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

CVE-2026-41567GHSA-x86f-5xw2-fm2r

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/moby/moby/v2

    Affected
    < 2.0.0-beta.14
    Fixed in
    2.0.0-beta.14

  • Go github.com/docker/docker

    Affected
    <= 28.5.2
    Fixed in
    no fixed version recorded

  • Go github.com/moby/moby

    Affected
    <= 28.5.2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.2 · CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N
EPSS
  • CVE-2026-41567: 0.15% estimated exploitation activity in the next 30 days; percentile 4.64 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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)…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-x86f-5xw2-fm2r

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41567

Advisory: Docker: `PUT /containers/{id}/archive` executes container binary on the host
IDs: CVE-2026-41567, GHSA-x86f-5xw2-fm2r
Record: https://patchnext.com/advisories/cve-2026-41567 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/moby/moby/v2 2.0.0-beta.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/moby/moby/v2: affected < 2.0.0-beta.14; fixed in 2.0.0-beta.14
- Go github.com/docker/docker: affected <= 28.5.2
- Go github.com/moby/moby: affected <= 28.5.2

## Suggested inspection (read-only)
- Go github.com/moby/moby/v2: check the installed version with your package manager.
- Go github.com/docker/docker: check the installed version with your package manager.
- Go github.com/moby/moby: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/moby/moby/v2, github.com/docker/docker, github.com/moby/moby.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x86f-5xw2-fm2r (GitHub-reviewed advisory GHSA-x86f-5xw2-fm2r lists affected ranges: Go github.com/moby/moby/v2 >=0 =0 =0 <=28.5.2)

Commands are suggestions: review each one before running it.

Loading voting…