CVE-2025-15558: CWE-427 Uncontrolled Search Path Element in Docker Docker CLI
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.
AI Analysis
Technical Summary
CVE-2025-15558 is a vulnerability classified under CWE-427 (Uncontrolled Search Path Element) affecting Docker CLI on Windows platforms up to version 29.1.5. The issue arises because the Docker CLI searches for plugin binaries in the directory C:\ProgramData\Docker\cli-plugins, which is not created by default. This allows a low-privileged attacker with local access to create this directory and place malicious executables named as legitimate Docker CLI plugins (e.g., docker-compose.exe, docker-buildx.exe). When a victim user launches Docker Desktop or invokes Docker CLI plugin features, the malicious binaries are executed. If the Docker CLI is running with elevated privileges, this can lead to privilege escalation, allowing the attacker to execute arbitrary code with higher privileges. The vulnerability is specific to Windows binaries that use the github.com/docker/cli/cli-plugins/manager package for plugin management and does not affect non-Windows versions or projects not using this plugin manager. The CVSS 4.0 score is 7.0 (high), reflecting local attack vector with low complexity, no authentication required, but user interaction needed. The vulnerability impacts confidentiality, integrity, and availability due to potential arbitrary code execution and privilege escalation. No patches or exploits in the wild are currently reported, but the risk is significant given Docker's widespread use in development and production environments on Windows.
Potential Impact
This vulnerability poses a significant risk to organizations using Docker CLI on Windows, especially those running Docker Desktop or CLI with elevated privileges. Successful exploitation can lead to privilege escalation, allowing attackers to execute arbitrary code with higher system privileges. This can compromise the confidentiality and integrity of sensitive data, disrupt containerized application workflows, and potentially allow attackers to pivot within the network. Since Docker is widely used in development, testing, and production environments, exploitation could affect software supply chains and continuous integration/continuous deployment (CI/CD) pipelines. The requirement for local access and user interaction limits remote exploitation but insider threats or compromised low-privileged accounts could leverage this vulnerability. Organizations relying on Windows-based Docker environments are at risk of operational disruption and data breaches if this vulnerability is exploited.
Mitigation Recommendations
Organizations should immediately verify if Docker CLI on Windows is deployed and check the presence of the C:\ProgramData\Docker\cli-plugins directory. If it exists and is writable by low-privileged users, restrict permissions to prevent unauthorized creation or modification of plugin binaries. Run Docker CLI and Docker Desktop with the least privilege necessary, avoiding elevated privileges unless absolutely required. Monitor and audit the cli-plugins directory for unexpected files or changes. Until an official patch is released, consider disabling plugin features or using Docker CLI on non-Windows platforms where this vulnerability does not exist. Implement endpoint detection and response (EDR) solutions to detect suspicious execution of Docker CLI plugins. Educate users about the risk of running Docker CLI with elevated privileges and the importance of reporting unexpected Docker behavior. Stay updated with Docker vendor advisories for patches and apply them promptly once available.
Affected Countries
United States, Germany, United Kingdom, France, Canada, Australia, Japan, South Korea, India, Brazil
CVE-2025-15558: CWE-427 Uncontrolled Search Path Element in Docker Docker CLI
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-15558 is a vulnerability classified under CWE-427 (Uncontrolled Search Path Element) affecting Docker CLI on Windows platforms up to version 29.1.5. The issue arises because the Docker CLI searches for plugin binaries in the directory C:\ProgramData\Docker\cli-plugins, which is not created by default. This allows a low-privileged attacker with local access to create this directory and place malicious executables named as legitimate Docker CLI plugins (e.g., docker-compose.exe, docker-buildx.exe). When a victim user launches Docker Desktop or invokes Docker CLI plugin features, the malicious binaries are executed. If the Docker CLI is running with elevated privileges, this can lead to privilege escalation, allowing the attacker to execute arbitrary code with higher privileges. The vulnerability is specific to Windows binaries that use the github.com/docker/cli/cli-plugins/manager package for plugin management and does not affect non-Windows versions or projects not using this plugin manager. The CVSS 4.0 score is 7.0 (high), reflecting local attack vector with low complexity, no authentication required, but user interaction needed. The vulnerability impacts confidentiality, integrity, and availability due to potential arbitrary code execution and privilege escalation. No patches or exploits in the wild are currently reported, but the risk is significant given Docker's widespread use in development and production environments on Windows.
Potential Impact
This vulnerability poses a significant risk to organizations using Docker CLI on Windows, especially those running Docker Desktop or CLI with elevated privileges. Successful exploitation can lead to privilege escalation, allowing attackers to execute arbitrary code with higher system privileges. This can compromise the confidentiality and integrity of sensitive data, disrupt containerized application workflows, and potentially allow attackers to pivot within the network. Since Docker is widely used in development, testing, and production environments, exploitation could affect software supply chains and continuous integration/continuous deployment (CI/CD) pipelines. The requirement for local access and user interaction limits remote exploitation but insider threats or compromised low-privileged accounts could leverage this vulnerability. Organizations relying on Windows-based Docker environments are at risk of operational disruption and data breaches if this vulnerability is exploited.
Mitigation Recommendations
Organizations should immediately verify if Docker CLI on Windows is deployed and check the presence of the C:\ProgramData\Docker\cli-plugins directory. If it exists and is writable by low-privileged users, restrict permissions to prevent unauthorized creation or modification of plugin binaries. Run Docker CLI and Docker Desktop with the least privilege necessary, avoiding elevated privileges unless absolutely required. Monitor and audit the cli-plugins directory for unexpected files or changes. Until an official patch is released, consider disabling plugin features or using Docker CLI on non-Windows platforms where this vulnerability does not exist. Implement endpoint detection and response (EDR) solutions to detect suspicious execution of Docker CLI plugins. Educate users about the risk of running Docker CLI with elevated privileges and the importance of reporting unexpected Docker behavior. Stay updated with Docker vendor advisories for patches and apply them promptly once available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Docker
- Date Reserved
- 2026-02-03T19:51:18.184Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69a85ed0d1a09e29cb4aedd6
Added to database: 3/4/2026, 4:33:20 PM
Last enriched: 3/11/2026, 7:57:35 PM
Last updated: 4/19/2026, 11:00:41 AM
Views: 70
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.