How severe is CVE-2026-41567?

CVE-2026-41567 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over local access with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-41567 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-41567?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-41567 have an EU (EUVD) identifier?

Yes. CVE-2026-41567 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-34779.

When was CVE-2026-41567 published?

CVE-2026-41567 was published on 2026-06-05 and last updated on 2026-07-06.

CVE-2026-41567

CVE-2026-41567 is a high-severity vulnerability with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-427.

Key facts

Severity: High (CVSS 3.x base score 7.2)
EPSS exploit prediction: 0% (5th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-34779
Weakness: CWE-427
Published: 2026-06-05
Last modified: 2026-07-06

Description

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

Frequently asked questions

What is CVE-2026-41567?: 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
How severe is CVE-2026-41567?: CVE-2026-41567 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over local access with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-41567 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-41567?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-41567 have an EU (EUVD) identifier?: Yes. CVE-2026-41567 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-34779.
When was CVE-2026-41567 published?: CVE-2026-41567 was published on 2026-06-05 and last updated on 2026-07-06.

References

Other CWE-427 (Uncontrolled Search Path Element) vulnerabilities

CVE-2025-4981 — Critical (CVSS 9.9): Mattermost versions 10.5.x <= 10.5.5, 9.11.x <= 9.11.15, 10.8.x <= 10.8.0, 10.7.x <= 10.7.2, 10.6.x <= 10.6.5 fail to…
CVE-2025-69599 — Critical (CVSS 9.8): RayVentory Scan Engine through 12.6 Update 8 allows attackers to gain privileges if they control the value of the PATH…
CVE-2019-25268 — Critical (CVSS 9.8): NREL BEopt 2.8.0.0 contains a DLL hijacking vulnerability that allows attackers to load arbitrary libraries by tricking…
CVE-2023-53959 — Critical (CVSS 9.8): FileZilla Client 3.63.1 contains a DLL hijacking vulnerability that allows attackers to execute malicious code by…
CVE-2025-65741 — Critical (CVSS 9.8): Sublime Text 3 Build 3208 or prior for MacOS is vulnerable to Dylib Injection. An attacker could compile a .dylib file…
CVE-2024-23054 — Critical (CVSS 9.8): An issue in Plone Docker Official Image 5.2.13 (5221) open-source software that could allow for remote code execution…

Browse all CWE-427 (Uncontrolled Search Path Element) vulnerabilities →