CVE-2025-15558: Docker Desktop Docker Plugins Uncontrolled Search Path Element Local Privilege Escalation Vulnerability
Docker CLI for Windows searches for plugin binaries in C:\ProgramData\Docker\cli-plugins, a directory that does not exist by default. A low-privileged attacker can create this directory and place malicious CLI plugin binaries (docker-compose.exe, docker-buildx.exe, etc.) that are executed when a victim user opens Docker Desktop or invokes Docker CLI plugin features, and allow privilege-escalation if the docker CLI is executed as a privileged user.
This issue affects Docker CLI: through 29.1.5 and Windows binaries acting as a CLI-plugin manager using the github.com/docker/cli/cli-plugins/manager https://pkg.go.dev/github.com/docker/cli@v29.1.5+incompatible/cli-plugins/manager package, such as Docker Compose.
This issue does not impact non-Windows binaries, and projects not using the plugin-manager code.
Security readout for executives and security teams
Plain-English summary
On Windows, Docker CLI can look for plugin programs in a global folder that may not exist by default. A low-privileged local attacker could create that folder and place malicious plugin binaries there. If a more privileged user later opens Docker Desktop or uses Docker plugin features, those binaries could run with that user’s privileges.
Executive priority
Treat this as high priority for Windows developer fleets and privileged build hosts. It is not remotely exploitable from the supplied evidence, but it can turn a low-privileged local foothold into administrator-level impact when Docker is used elevated.
Technical view
CVE-2025-15558 is a CWE-427 uncontrolled search path issue in Docker CLI plugin discovery on Windows. The reported path is C:\ProgramData\Docker\cli-plugins. Sources describe Docker CLI through 29.1.5 and Windows binaries using Docker’s cli-plugins manager as in scope; non-Windows binaries and projects not using that code are out of scope.
Likely exposure
Exposure is mainly Windows developer or build workstations running Docker Desktop, Docker CLI, or related Windows binaries using Docker’s CLI plugin manager. Risk increases where Docker commands are run elevated or by administrator accounts. Non-Windows deployments are not indicated as affected in the provided sources.
Exploitation context
The CVSS vector is local, low complexity, low privilege required, and user interaction required. The bundle marks KEV as false, and no cited source in the bundle establishes active exploitation. This should be treated as plausible local privilege escalation, not confirmed in-the-wild exploitation.
Researcher notes
There is some version ambiguity in the supplied bundle: the description says Docker CLI through 29.1.5, while the affected metadata lists Docker CLI 29.2.0 as affected and Compose 5.1.0 as unaffected. Validate final affected and fixed versions from Docker sources before enforcement.
Mitigation direction
Review Docker release notes and apply the vendor-fixed Docker Desktop or Docker CLI version.
Prioritize Windows systems where Docker CLI is run with administrative privileges.
Restrict creation and modification of C:\ProgramData\Docker\cli-plugins where feasible.
Audit third-party Windows binaries that use Docker’s cli-plugins manager package.
If no fixed version is confirmed, follow Docker’s advisory and release guidance.
Validation and detection
Inventory Windows hosts with Docker Desktop, Docker CLI, Docker Compose, or Docker plugin-manager consumers.
Check installed Docker CLI versions against vendor release notes and the CVE record.
Inspect C:\ProgramData\Docker\cli-plugins permissions and unexpected plugin binaries.
Confirm whether users or automation run Docker commands elevated.
Monitor endpoint telemetry for unexpected Docker plugin binary execution from ProgramData.
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.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
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
7Source 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.
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.