CVE-2026-2664 is an out-of-bounds read vulnerability in the grpcfuse kernel module within the Linux VM used by Docker Desktop on Windows, Linux, and macOS up to version 4.61.0. This vulnerability allows a local attacker with low privileges to cause an unspecified impact by writing to /proc/docker entries. The issue has been addressed and fixed in Docker Desktop version 4.62.0. The vulnerability has a CVSS 4.0 base score of 6.8, indicating a medium severity level.
Docker Desktop for Windows contains multiple incorrect permission assignment vulnerabilities in the installer's handling of the C:\ProgramData\DockerDesktop directory. The installer creates this directory without proper ownership verification, creating two exploitation scenarios:
Scenario 1 (Persistent Attack):
If a low-privileged attacker pre-creates C:\ProgramData\DockerDesktop before Docker Desktop installation, the attacker retains ownership of the directory even after the installer applies restrictive ACLs. At any time after installation completes, the attacker can modify the directory ACL (as the owner) and tamper with critical configuration files such as install-settings.json to specify a malicious credentialHelper, causing arbitrary code execution when any user runs Docker Desktop.
Scenario 2 (TOCTOU Attack):
During installation, there is a time-of-check-time-of-use (TOCTOU) race condition between when the installer creates C:\ProgramData\DockerDesktop and when it sets secure ACLs. A low-privileged attacker actively monitoring for the installation can inject malicious files (such as install-settings.json) with attacker-controlled ACLs during this window, achieving the same code execution outcome.
Docker Desktop diagnostics bundles were found to include expired Hub PATs in log output due to error object serialization. This poses a risk of leaking sensitive information in exported diagnostics, especially when access denied errors occurred.
CVE-2025-64443 is a high-severity vulnerability in docker's MCP Gateway versions prior to 0.28.0, caused by DNS rebinding when running in sse or streaming transport modes. This flaw allows attackers to exploit browser-based access to MCP servers behind the gateway by tricking victims into visiting malicious websites or ads, enabling manipulation of exposed tools and features. The default stdio mode is not affected as it does not listen on network ports. No known exploits are currently in the wild, and the vulnerability was fixed in version 0.28.0. The vulnerability has a CVSS 4.0 score of 7.
CVE-2025-62725 is a path traversal vulnerability in Docker Compose that allows an attacker to escape the local cache directory and overwrite arbitrary files on the host machine. This occurs because Docker Compose trusts path information embedded in remote OCI compose artifacts and improperly joins attacker-supplied values with local paths. The vulnerability affects multiple platforms and workflows that resolve remote OCI compose artifacts, including Docker Desktop, standalone Compose binaries on Linux, CI/CD runners, and cloud development environments. The issue is fixed in Docker Compose version 2.40.2.
Docker Desktop Installer.exe is vulnerable to DLL hijacking due to insecure DLL search order. The installer searches for required DLLs in the user's Downloads folder before checking system directories, allowing local privilege escalation through malicious DLL placement.This issue affects Docker Desktop: through 4.48.0.
In a hardened Docker environment, with Enhanced Container Isolation ( ECI https://docs.docker.com/enterprise/security/hardened-desktop/enhanced-container-isolation/ ) enabled, an administrator can utilize the command restrictions feature https://docs.docker.com/enterprise/security/hardened-desktop/enhanced-container-isolation/config/#command-restrictions to restrict commands that a container with a Docker socket mount may issue on that socket.
Due to a software bug, the configuration to restrict commands was ignored when passed to ECI, allowing any command to be executed on the socket. This grants excessive privileges by permitting unrestricted access to powerful Docker commands.
The vulnerability affects only Docker Desktop 4.46.0 users that have ECI enabled and are using the Docker socket command restrictions feature. In addition, since ECI restricts mounting the Docker socket into containers by default, it only affects containers which are explicitly allowed by the administrator to mount the Docker socket.
A vulnerability was identified in Docker Desktop that allows local running Linux containers to access the Docker Engine API via the configured Docker subnet, at 192.168.65.7:2375 by default. This vulnerability occurs with or without Enhanced Container Isolation (ECI) enabled, and with or without the "Expose daemon on tcp://localhost:2375 without TLS" option enabled.
This can lead to execution of a wide range of privileged commands to the engine API, including controlling other containers, creating new ones, managing images etc. In some circumstances (e.g. Docker Desktop for Windows with WSL backend) it also allows mounting the host drive with the same privileges as the user running Docker Desktop.
System environment variables are recorded in Docker Desktop diagnostic logs, when using shell auto-completion. This leads to unintentional disclosure of sensitive information such as api keys, passwords, etc.
A malicious actor with read access to these logs could obtain secrets and further use them to gain unauthorized access to other systems. Starting with version 4.43.0 Docker Desktop no longer logs system environment variables as part of diagnostics log collection.
Docker Desktop Community Edition contains a local privilege escalation vulnerability where an attacker can place a malicious docker-credential-wincred.exe file in a specific directory to escalate privileges.