Skip to content
Noroxi
CVE-2026-41567· NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 28/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
  • Fixed version: docker.io (Debian:13) 26.1.5+dfsg1-9+deb13u1; docker.io (Debian:14) 28.5.2+dfsg4-3; github.com/moby/moby/v2 (Go) 2.0.0-beta.14.

Low priority for now. Upgrade to docker.io (Debian:13) 26.1.5+dfsg1-9+deb13u1; docker.io (Debian:14) 28.5.2+dfsg4-3; github.com/moby/moby/v2 (Go) 2.0.0-beta.14 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.2 · v3.1—Proof of concept Fix available
Published
Jun 4, 2026
Updated
Sep 9, 2026
EPSS
0.1% · 4th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
7.2
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-41567

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for moby records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
multicluster globalhub1.4
multicluster globalhub1.6
source to image1.6
multicluster globalhub1.5
openshift data foundation4.22
exploit intelligence0
multicluster engine
openshift lightspeed
acm2
ceph storage5
ceph storage7
ceph storage8

and 7 more

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • docker docker/daemon

    • <= 28.5.2affected

  • moby Docker Engine

    • < 29.5.1affected

  • moby moby/v2/daemon

    • < 2.0.0-beta.14affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12docker.iofrom 0—
Debian:13docker.iobefore 26.1.5+dfsg1-9+deb13u126.1.5+dfsg1-9+deb13u1
Debian:14docker.iobefore 28.5.2+dfsg4-328.5.2+dfsg4-3
Gogithub.com/docker/dockerfrom 0—
Gogithub.com/docker/dockerup to and including 28.5.2—
Gogithub.com/moby/mobyfrom 0—
Gogithub.com/moby/mobyup to and including 28.5.2—
Gogithub.com/moby/moby/v2before 2.0.0-beta.142.0.0-beta.14
openSUSE:Leap 16.0dockerbefore 29.4.0_ce-160000.7.129.4.0_ce-160000.7.1
openSUSE:Leap 16.0docker-stablebefore 24.0.9_ce-160000.6.124.0.9_ce-160000.6.1
openSUSE:Tumbleweeddockerbefore 29.4.0_ce-40.129.4.0_ce-40.1
openSUSE:Tumbleweeddocker-stablebefore 24.0.9_ce-18.124.0.9_ce-18.1
SUSE:Linux Enterprise Micro 5.3dockerbefore 29.4.0_ce-150000.253.129.4.0_ce-150000.253.1
SUSE:Linux Enterprise Module for Containers 15 SP7docker-stablebefore 24.0.9_ce-150000.1.48.124.0.9_ce-150000.1.48.1
SUSE:Linux Enterprise Server 12 SP5-LTSSdocker-stablebefore 24.0.9_ce-1.40.124.0.9_ce-1.40.1
SUSE:Linux Micro 6.0dockerbefore 29.4.0_ce-11.129.4.0_ce-11.1
SUSE:Linux Micro 6.1dockerbefore 29.4.0_ce-slfo.1.1_10.129.4.0_ce-slfo.1.1_10.1
SUSE:Linux Micro 6.2dockerbefore 29.4.0_ce-160000.7.129.4.0_ce-160000.7.1

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:docker.io26.1.5+dfsg1-9+deb13u1 · Debian:13Package registry (OSV)
Go:github.com/moby/moby/v22.0.0-beta.14Package registry (OSV)
opensuse:docker29.4.0_ce-40.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:docker-stable24.0.9_ce-18.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:docker29.4.0_ce-160000.7.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:docker-stable24.0.9_ce-1.40.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-08-21

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+77 d
  3. TodayOct 21, 2026+139 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-427 · Uncontrolled Search Path Element

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records