moby/v2/daemon: Uncontrolled Search Path Element
CVE-2026-41567 is a high-severity uncontrolled search path element vulnerability in moby/v2/daemon from Moby, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, but only if a user takes part, for example by opening a link or file. Affected moby/v2/daemon versions: < 2.0.0-beta.14. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.32% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of moby/v2/daemon you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Moby | moby/v2/daemon | < 2.0.0-beta.14 | Not stated |
| Moby | Docker Engine | < 29.5.1 | Not stated |
| Docker | docker/daemon | <= 28.5.2 | Not stated |
| Red Hat | Multicluster Global Hub 1.4.5 | Not specified in the record | Not stated |
| Red Hat | Multicluster Global Hub 1.6.5 | Not specified in the record | Not stated |
| Red Hat | OpenShift Developer Tools and Services 1.6.3 | Not specified in the record | Not stated |
| Red Hat | Red Hat multicluster global hub 1.5.3 | Not specified in the record | Not stated |
| Red Hat | Red Hat Openshift Data Foundation 4.22 | Not specified in the record | Not stated |
| Red Hat | Exploit Intelligence | Not specified in the record | Not stated |
| Red Hat | Multicluster Engine for Kubernetes | Not specified in the record | Not stated |
| Red Hat | OpenShift Lightspeed | Not specified in the record | Not stated |
| Red Hat | Red Hat Advanced Cluster Management for Kubernetes 2 | Not specified in the record | Not stated |
| Red Hat | Red Hat Ceph Storage 5 | Not specified in the record | Not stated |
| Red Hat | Red Hat Ceph Storage 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat Ceph Storage 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Ceph Storage 9 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 10 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9 | Not specified in the record | Not stated |
| Red Hat | Red Hat Hardened Images | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift AI (RHOAI) | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift distributed tracing 3 | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N. Scored by CNA (github.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.2 | High | CNA (github.com) |
| CVSS 3.1 | 7.5 | High | CNA |
Official 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
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Uncontrolled Search Path Element
The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.
How developers prevent this class of flaw
- Hard-code the search path to a set of known-safe values (such as system directories), or only allow them to be specified by the administrator in a configuration file. Do not allow these settings to be modified by an external party. Be careful to avoid related weaknesses such as CWE-426 and CWE-428.
- When invoking other programs, specify those programs using fully-qualified pathnames. While this is an effective approach, code that uses fully-qualified pathnames might not be portable to other systems that do not use the same pathnames. The portability can be improved by locating the full-qualified paths in a centralized, easily-modifiable location within the source code, and having the code refer to these paths.
- Remove or restrict all environment settings before invoking other programs. This includes the PATH environment variable, LD_LIBRARY_PATH, and other settings that identify the location of code libraries, and any application-specific search paths.
More Uncontrolled Search Path Element vulnerabilities (CWE-427)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
- access.redhat.com/errata/RHSA-2026:37387
- access.redhat.com/errata/RHSA-2026:41030
- access.redhat.com/errata/RHSA-2026:42852
- access.redhat.com/errata/RHSA-2026:44622
- access.redhat.com/errata/RHSA-2026:51057
- access.redhat.com/security/cve/CVE-2026-41567
- bugzilla.redhat.com/show_bug.cgi?id=2485356
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-41567.json
Recent Uncontrolled Search Path Element vulnerabilities
- 7.3 High severity
- 7.3 High severity
- 7.3 High severity
- 8.2 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.