Docker

Known Exploited Docker Vulnerabilities

The following Docker vulnerabilities have been marked by CISA as Known to be Exploited by threat actors.

The vulnerability CVE-2019-15752: Docker Desktop Community Edition Privilege Escalation Vulnerability is in the top 5% of the currently known exploitable vulnerabilities.

By the Year

In 2026 there have been 0 vulnerabilities in Docker. Last year, in 2025 Docker had 11 security vulnerabilities published. Right now, Docker is on track to have less security vulnerabilities in 2026 than it did last year.

Recent Docker Security Vulnerabilities

CVE	Date	Vulnerability	Products
CVE-2025-13743	Dec 09, 2025	Docker Desktop Diagnostics Leak Expired Hub PATs via Error Object Serialization 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.	Docker Desktop
CVE-2025-64443	Dec 03, 2025	DNS Rebinding in MCP Gateway <0.28.0 (p0s0.27) sse/streaming modes MCP Gateway allows easy and secure running and deployment of MCP servers. In versions 0.27.0 and earlier, when MCP Gateway runs in sse or streaming transport mode, it is vulnerable to DNS rebinding. An attacker who can get a victim to visit a malicious website or be served a malicious advertisement can perform browser-based exploitation of MCP servers executing behind the gateway, including manipulating tools or other features exposed by those MCP servers. MCP Gateway is not affected when running in the default stdio mode, which does not listen on network ports. Version 0.28.0 fixes this issue.
CVE-2025-62725	Oct 27, 2025	Docker Compose Remote OCI Path Traversal (v2.39 & earlier) Docker Compose trusts the path information embedded in remote OCI compose artifacts. When a layer includes the annotations com.docker.compose.extends or com.docker.compose.envfile, Compose joins the attackersupplied value from com.docker.compose.file/com.docker.compose.envfile with its local cache directory and writes the file there. This affects any platform or workflow that resolves remote OCI compose artifacts, Docker Desktop, standalone Compose binaries on Linux, CI/CD runners, cloud dev environments is affected. An attacker can escape the cache directory and overwrite arbitrary files on the machine running docker compose, even if the user only runs readonly commands such as docker compose config or docker compose ps. This issue is fixed in v2.40.2.	Compose
CVE-2025-9164	Oct 27, 2025	Docker Desktop DLL hijacking via Installer.exe (before 4.48.0) 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.	Docker Desktop
CVE-2025-10657	Sep 26, 2025	Docker Desktop 4.46.0: ECI Cmd Restriction Bypass Grants Full Socket Access 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.	Docker Desktop
CVE-2025-9074	Aug 20, 2025	Docker Desktop: Containers access Engine API on 192.168.65.7:2375 (CVE-2025-9074) 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.	Docker Desktop
CVE-2025-6587	Jul 03, 2025	Docker Desktop 4.43.0 prevents env var leak in diag logs 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
CVE-2025-4095	Apr 29, 2025	Docker Desktop MacOS RAM Policy Bypass Allows Unrestricted Registry Pull Registry Access Management (RAM) is a security feature allowing administrators to restrict access for their developers to only allowed registries. When a MacOS configuration profile is used to enforce organization sign-in, the RAM policies are not being applied, which would allow Docker Desktop users to pull down unapproved, and potentially malicious images from any registry.	Docker Desktop
CVE-2025-3911	Apr 29, 2025	Docker Desktop ENV Variable Leak <4.41.0 Recording of environment variables, configured for running containers, in Docker Desktop application logs could lead to unintentional disclosure of sensitive information such as api keys, passwords, etc. A malicious actor with read access to these logs could obtain sensitive credentials information and further use it to gain unauthorized access to other systems. Starting with version 4.41.0, Docker Desktop no longer logs environment variables set by the user.	Docker Desktop
CVE-2025-3224	Apr 28, 2025	Docker Desktop for Windows <4.41.0: Local Priv Esc via Config Manipulation A vulnerability in the update process of Docker Desktop for Windows versions prior to 4.41.0 could allow a local, low-privileged attacker to escalate privileges to SYSTEM. During an update, Docker Desktop attempts to delete files and subdirectories under the path C:\ProgramData\Docker\config with high privileges. However, this directory often does not exist by default, and C:\ProgramData\ allows normal users to create new directories. By creating a malicious Docker\config folder structure at this location, an attacker can force the privileged update process to delete or manipulate arbitrary system files, leading to Elevation of Privilege.	Desktop Docker Desktop
CVE-2025-1696	Mar 06, 2025	Docker Desktop <4.39.0 Log Disclosure of Proxy Info via Clear-Text Logs A vulnerability exists in Docker Desktop prior to version 4.39.0 that could lead to the unintentional disclosure of sensitive information via application logs. In affected versions, proxy configuration datapotentially including sensitive detailswas written to log files in clear text whenever an HTTP GET request was made through a proxy. An attacker with read access to these logs could obtain the proxy information and leverage it for further attacks or unauthorized access. Starting with version 4.39.0, Docker Desktop no longer logs the proxy string, thereby mitigating this risk.	Docker Desktop
CVE-2024-41968	Nov 18, 2024	Low-Privilege Remote Attacker Modifies Docker Settings Limited DoS A low privileged remote attacker may modify the docker settings setup of the device, leading to a limited DoS.	Docker
CVE-2024-9348	Oct 16, 2024	Docker Desktop <4.34.3 RCE via Unsanitized GitHub Link Docker Desktop before v4.34.3 allows RCE via unsanitized GitHub source link in Build view.	Docker Desktop
CVE-2024-9407	Oct 01, 2024	Docker RUN --mount Vulnerable Bind-Propagation Bypass CVE-2024-9407 A vulnerability exists in the bind-propagation option of the Dockerfile RUN --mount instruction. The system does not properly validate the input passed to this option, allowing users to pass arbitrary parameters to the mount instruction. This issue can be exploited to mount sensitive directories from the host into a container during the build process and, in some cases, modify the contents of those mounted files. Even if SELinux is used, this vulnerability can bypass its protection by allowing the source directory to be relabeled to give the container access to host files.	Docker
CVE-2024-8695	Sep 12, 2024	RCE via crafted extension description in Docker Desktop v<4.34.2 A remote code execution (RCE) vulnerability via crafted extension description/changelog could be abused by a malicious extension in Docker Desktop before 4.34.2.	Desktop Docker Desktop
CVE-2024-8696	Sep 12, 2024	RCE via crafted extension publisher-url in Docker Desktop <4.34.2 A remote code execution (RCE) vulnerability via crafted extension publisher-url/additional-urls could be abused by a malicious extension in Docker Desktop before 4.34.2.	Desktop Docker Desktop
CVE-2024-6222	Jul 09, 2024	Docker Desktop IPC Escalation via Extensions ( v4.28) In Docker Desktop before v4.29.0, an attacker who has gained access to the Docker Desktop VM through a container breakout can further escape to the host by passing extensions and dashboard related IPC messages. Docker Desktop v4.29.0 https://docs.docker.com/desktop/release-notes/#4290 fixes the issue on MacOS, Linux and Windows with Hyper-V backend. As exploitation requires "Allow only extensions distributed through the Docker Marketplace" to be disabled, Docker Desktop  v4.31.0 https://docs.docker.com/desktop/release-notes/#4310  additionally changes the default configuration to enable this setting by default.	Desktop
CVE-2024-5652	Jul 09, 2024	Docker Desktop Windows <4.31.0 exec-path DoS via docker-users In Docker Desktop on Windows before v4.31.0 allows a user in the docker-users group to cause a Windows Denial-of-Service through the exec-path Docker daemon config option in Windows containers mode.	Desktop Docker Desktop
CVE-2024-24557	Feb 01, 2024	Docker Moby Classic Builder Cache Poisoning (23.x and <23.0, fixed 24.0.9/25.0.2) Moby is an open-source project created by Docker to enable software containerization. The classic builder cache system is prone to cache poisoning if the image is built FROM scratch. Also, changes to some instructions (most important being HEALTHCHECK and ONBUILD) would not cause a cache miss. An attacker with the knowledge of the Dockerfile someone is using could poison their cache by making them pull a specially crafted image that would be considered as a valid cache candidate for some build steps. 23.0+ users are only affected if they explicitly opted out of Buildkit (DOCKER_BUILDKIT=0 environment variable) or are using the /build API endpoint. All users on versions older than 23.0 could be impacted. Image build API endpoint (/build) and ImageBuild function from github.com/docker/docker/client is also affected as it the uses classic builder by default. Patches are included in 24.0.9 and 25.0.2 releases.	Docker
CVE-2023-40453	Nov 07, 2023	Docker Machine <=0.16.2 EscSeq Injection & DoS via Crafted Version Data Docker Machine through 0.16.2 allows an attacker, who has control of a worker node, to provide crafted version data, which might potentially trick an administrator into performing an unsafe action (via escape sequence injection), or might have a data size that causes a denial of service to a bastion node. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.	Machine
CVE-2023-5165	Sep 25, 2023	Docker Desktop <4.23.0 Unprivileged ECI Bypass via Debug Shell Docker Desktop before 4.23.0 allows an unprivileged user to bypass Enhanced Container Isolation (ECI) restrictions via the debug shell which remains accessible for a short time window after launching Docker Desktop. The affected functionality is available for Docker Business customers only and assumes an environment where users are not granted local root or Administrator privileges. This issue has been fixed in Docker Desktop 4.23.0. Affected Docker Desktop versions: from 4.13.0 before 4.23.0.	Docker Desktop
CVE-2023-5166	Sep 25, 2023	Docker Desktop (<4.23.0): Access Token theft via crafted extension icon URL Docker Desktop before 4.23.0 allows Access Token theft via a crafted extension icon URL. This issue affects Docker Desktop: before 4.23.0.	Docker Desktop
CVE-2023-0625	Sep 25, 2023	RCE via Crafted Extension Description in Docker Desktop <4.12.0 Docker Desktop before 4.12.0 is vulnerable to RCE via a crafted extension description or changelog. This issue affects Docker Desktop: before 4.12.0.	Docker Desktop
CVE-2023-0626	Sep 25, 2023	Docker Desktop RCE via query parameters in message-box route (4.11) Docker Desktop before 4.12.0 is vulnerable to RCE via query parameters in message-box route. This issue affects Docker Desktop: before 4.12.0.	Docker Desktop
CVE-2023-0627	Sep 25, 2023	Docker Desktop 4.11.x LPE via IPC spoofing (--no-windows-containers flag) Docker Desktop 4.11.x allows --no-windows-containers flag bypass via IPC response spoofing which may lead to Local Privilege Escalation (LPE).This issue affects Docker Desktop: 4.11.X.	Docker Desktop
CVE-2023-0633	Sep 25, 2023	Docker Desktop 4.11 & older: Installer Argument Injection LPE In Docker Desktop on Windows before 4.12.0 an argument injection to installer may result in local privilege escalation (LPE).This issue affects Docker Desktop: before 4.12.0.	Docker Desktop
CVE-2021-25749	May 24, 2023	Docker Windows Containers: RunAsNonRoot Ignored, Enabling Admin Privileges Windows workloads can run as ContainerAdministrator even when those workloads set the runAsNonRoot option to true.	Docker
CVE-2022-31647	Apr 27, 2023	Docker Desktop <4.6.0 Windows Symlink File Deletion via hyperv API Docker Desktop before 4.6.0 on Windows allows attackers to delete any file through the hyperv/destroy dockerBackendV2 API via a symlink in the DataFolder parameter, a different vulnerability than CVE-2022-26659.	Desktop Docker Desktop
CVE-2022-34292	Apr 27, 2023	Docker Desktop Windows <4.6.0: Symlink Attack via dockerBackendV2 API Docker Desktop for Windows before 4.6.0 allows attackers to overwrite any file through a symlink attack on the hyperv/create dockerBackendV2 API by controlling the DataFolder parameter for DockerDesktop.vhdx, a similar issue to CVE-2022-31647.	Desktop Docker Desktop
CVE-2022-37326	Apr 27, 2023	Privilege Escalation via pidfile in Docker Desktop Win 4.6.0 API Docker Desktop for Windows before 4.6.0 allows attackers to delete (or create) any file through the dockerBackendV2 windowscontainers/start API by controlling the pidfile field inside the DaemonJSON field in the WindowsContainerStartRequest class. This can indirectly lead to privilege escalation.	Desktop Docker Desktop
CVE-2022-38730	Apr 27, 2023	Docker Desktop <4.6 (Win): TOCTOU File Overwrite via windowscontainers/start API Docker Desktop for Windows before 4.6 allows attackers to overwrite any file through the windowscontainers/start dockerBackendV2 API by controlling the data-root field inside the DaemonJSON field in the WindowsContainerStartRequest class. This allows exploiting a symlink vulnerability in ..\dataRoot\network\files\local-kv.db because of a TOCTOU race condition.	Desktop Docker Desktop
CVE-2023-1802	Apr 06, 2023	Docker Desktop 4.17.x Plain-HTTP Credential Leak (CVE-2023-1802) In Docker Desktop 4.17.x the Artifactory Integration falls back to sending registry credentials over plain HTTP if the HTTPS health check has failed. A targeted network sniffing attack can lead to a disclosure of sensitive information. Only users who have Access Experimental Features enabled and have logged in to a private registry are affected.	Desktop Docker Desktop
CVE-2023-28841	Apr 04, 2023	Docker Overlay Network Encryption Bypass - Unencrypted Traffic Leak Moby is an open source container framework developed by Docker Inc. that is distributed as Docker, Mirantis Container Runtime, and various other downstream projects/products. The Moby daemon component (`dockerd`), which is developed as moby/moby is commonly referred to as *Docker*. Swarm Mode, which is compiled in and delivered by default in `dockerd` and is thus present in most major Moby downstreams, is a simple, built-in container orchestrator that is implemented through a combination of SwarmKit and supporting network code. The `overlay` network driver is a core feature of Swarm Mode, providing isolated virtual LANs that allow communication between containers and services across the cluster. This driver is an implementation/user of VXLAN, which encapsulates link-layer (Ethernet) frames in UDP datagrams that tag the frame with the VXLAN metadata, including a VXLAN Network ID (VNI) that identifies the originating overlay network. In addition, the overlay network driver supports an optional, off-by-default encrypted mode, which is especially useful when VXLAN packets traverses an untrusted network between nodes. Encrypted overlay networks function by encapsulating the VXLAN datagrams through the use of the IPsec Encapsulating Security Payload protocol in Transport mode. By deploying IPSec encapsulation, encrypted overlay networks gain the additional properties of source authentication through cryptographic proof, data integrity through check-summing, and confidentiality through encryption. When setting an endpoint up on an encrypted overlay network, Moby installs three iptables (Linux kernel firewall) rules that enforce both incoming and outgoing IPSec. These rules rely on the `u32` iptables extension provided by the `xt_u32` kernel module to directly filter on a VXLAN packet's VNI field, so that IPSec guarantees can be enforced on encrypted overlay networks without interfering with other overlay networks or other users of VXLAN. An iptables rule designates outgoing VXLAN datagrams with a VNI that corresponds to an encrypted overlay network for IPsec encapsulation. Encrypted overlay networks on affected platforms silently transmit unencrypted data. As a result, `overlay` networks may appear to be functional, passing traffic as expected, but without any of the expected confidentiality or data integrity guarantees. It is possible for an attacker sitting in a trusted position on the network to read all of the application traffic that is moving across the overlay network, resulting in unexpected secrets or user data disclosure. Thus, because many database protocols, internal APIs, etc. are not protected by a second layer of encryption, a user may use Swarm encrypted overlay networks to provide confidentiality, which due to this vulnerability this is no longer guaranteed. Patches are available in Moby releases 23.0.3, and 20.10.24. As Mirantis Container Runtime's 20.10 releases are numbered differently, users of that platform should update to 20.10.16. Some workarounds are available. Close the VXLAN port (by default, UDP port 4789) to outgoing traffic at the Internet boundary in order to prevent unintentionally leaking unencrypted traffic over the Internet, and/or ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.	Docker
CVE-2023-0628	Mar 13, 2023	Docker Desktop <=4.16 Exec via Malicious docker-desktop:// URL Docker Desktop before 4.17.0 allows an attacker to execute an arbitrary command inside a Dev Environments container during initialization by tricking a user to open a crafted malicious docker-desktop:// URL.	Docker Desktop
CVE-2023-0629	Mar 13, 2023	Docker Desktop <4.17.0 ECI Bypass via Raw Socket CLI Flag Docker Desktop before 4.17.0 allows an unprivileged user to bypass Enhanced Container Isolation (ECI) restrictions by setting the Docker host to docker.raw.sock, or npipe:////.pipe/docker_engine_linux on Windows, via the -H (--host) CLI flag or the DOCKER_HOST environment variable and launch containers without the additional hardening features provided by ECI. This would not affect already running containers, nor containers launched through the usual approach (without Docker's raw socket). The affected functionality is available for Docker Business customers only and assumes an environment where users are not granted local root or Administrator privileges. This issue has been fixed in Docker Desktop 4.17.0. Affected Docker Desktop versions: from 4.13.0 before 4.17.0.	Docker Desktop
CVE-2022-36109	Sep 09, 2022	Moby Docker Engine 20.10.17: Group Bypass CVE-2022-36109 Moby is an open-source project created by Docker to enable software containerization. A bug was found in Moby (Docker Engine) where supplementary groups are not set up properly. If an attacker has direct access to a container and manipulates their supplementary group access, they may be able to use supplementary group access to bypass primary group restrictions in some cases, potentially gaining access to sensitive information or gaining the ability to execute code in that container. This bug is fixed in Moby (Docker Engine) 20.10.18. Running containers should be stopped and restarted for the permissions to be fixed. For users unable to upgrade, this problem can be worked around by not using the `"USER $USERNAME"` Dockerfile instruction. Instead by calling `ENTRYPOINT ["su", "-", "user"]` the supplementary groups will be set up properly.	Docker
CVE-2021-45449	Jan 12, 2022	Docker Desktop version 4.3.0 and 4.3.1 has a bug Docker Desktop version 4.3.0 and 4.3.1 has a bug that may log sensitive information (access token or password) on the user's machine during login. This only affects users if they are on Docker Desktop 4.3.0, 4.3.1 and the user has logged in while on 4.3.0, 4.3.1. Gaining access to this data would require having access to the users local files.	Docker Desktop
CVE-2021-41092	Oct 04, 2021	Docker CLI is the command line interface for the docker container runtime Docker CLI is the command line interface for the docker container runtime. A bug was found in the Docker CLI where running `docker login my-private-registry.example.com` with a misconfigured configuration file (typically `~/.docker/config.json`) listing a `credsStore` or `credHelpers` that could not be executed would result in any provided credentials being sent to `registry-1.docker.io` rather than the intended private registry. This bug has been fixed in Docker CLI 20.10.9. Users should update to this version as soon as possible. For users unable to update ensure that any configured credsStore or credHelpers entries in the configuration file reference an installed credential helper that is executable and on the PATH.	Command Line Interface
CVE-2021-37841	Aug 12, 2021	Docker Desktop before 3.6.0 suffers from incorrect access control Docker Desktop before 3.6.0 suffers from incorrect access control. If a low-privileged account is able to access the server running the Windows containers, it can lead to a full container compromise in both process isolation and Hyper-V isolation modes. This security issue leads an attacker with low privilege to read, write and possibly even execute code inside the containers.	Desktop
CVE-2021-21284	Feb 02, 2021	In Docker before versions 9.03.15, 20.10.3 there is a vulnerability involving the --userns-remap option in which access to remapped root In Docker before versions 9.03.15, 20.10.3 there is a vulnerability involving the --userns-remap option in which access to remapped root allows privilege escalation to real root. When using "--userns-remap", if the root user in the remapped namespace has access to the host filesystem they can modify files under "/var/lib/docker/<remapping>" that cause writing files with extended privileges. Versions 20.10.3 and 19.03.15 contain patches that prevent privilege escalation from remapped user.	Docker
CVE-2021-21285	Feb 02, 2021	In Docker before versions 9.03.15, 20.10.3 there is a vulnerability in In Docker before versions 9.03.15, 20.10.3 there is a vulnerability in which pulling an intentionally malformed Docker image manifest crashes the dockerd daemon. Versions 20.10.3 and 19.03.15 contain patches that prevent the daemon from crashing.	Docker
CVE-2020-27534	Dec 30, 2020	util/binfmt_misc/check.go in Builder in Docker Engine before 19.03.9 calls os.OpenFile with a potentially unsafe qemu-check temporary pathname util/binfmt_misc/check.go in Builder in Docker Engine before 19.03.9 calls os.OpenFile with a potentially unsafe qemu-check temporary pathname, constructed with an empty first argument in an ioutil.TempDir call.	Docker
CVE-2020-35195	Dec 17, 2020	The official haproxy docker images before 1.8.18-alpine (Alpine specific) contain a blank password for a root user The official haproxy docker images before 1.8.18-alpine (Alpine specific) contain a blank password for a root user. System using the haproxy docker container deployed by affected versions of the docker image may allow a remote attacker to achieve root access with a blank password.	Haproxy Docker Image
CVE-2020-35184	Dec 17, 2020	The official composer docker images before 1.8.3 contain a blank password for a root user The official composer docker images before 1.8.3 contain a blank password for a root user. System using the composer docker container deployed by affected versions of the docker image may allow a remote attacker to achieve root access with a blank password.	Composer Composer Docker Image
CVE-2020-35197	Dec 17, 2020	The official memcached docker images before 1.5.11-alpine (Alpine specific) contain a blank password for a root user The official memcached docker images before 1.5.11-alpine (Alpine specific) contain a blank password for a root user. System using the memcached docker container deployed by affected versions of the docker image may allow a remote attacker to achieve root access with a blank password.	Memcached Docker Image
CVE-2020-35196	Dec 17, 2020	The official rabbitmq docker images before 3.7.13-beta.1-management-alpine (Alpine specific) contain a blank password for a root user The official rabbitmq docker images before 3.7.13-beta.1-management-alpine (Alpine specific) contain a blank password for a root user. System using the rabbitmq docker container deployed by affected versions of the docker image may allow a remote attacker to achieve root access with a blank password.	Rabbitmq Docker Image
CVE-2020-35186	Dec 17, 2020	The official adminer docker images before 4.7.0-fastcgi contain a blank password for a root user The official adminer docker images before 4.7.0-fastcgi contain a blank password for a root user. System using the adminer docker container deployed by affected versions of the docker image may allow a remote attacker to achieve root access with a blank password.	Adminer
CVE-2020-35185	Dec 17, 2020	The official ghost docker images before 2.16.1-alpine (Alpine specific) contain a blank password for a root user The official ghost docker images before 2.16.1-alpine (Alpine specific) contain a blank password for a root user. System using the ghost docker container deployed by affected versions of the docker image may allow a remote attacker to achieve root access with a blank password.	Ghost Alpine Docker Image
CVE-2020-35467	Dec 15, 2020	The Docker Docs Docker image through 2020-12-14 contains a blank password for the root user The Docker Docs Docker image through 2020-12-14 contains a blank password for the root user. Systems deployed using affected versions of the Docker Docs container may allow a remote attacker to achieve root access with a blank password.	Docs
CVE-2020-29591	Dec 11, 2020	Versions of the Official registry Docker images through 2.7.0 contain a blank password for the root user Versions of the Official registry Docker images through 2.7.0 contain a blank password for the root user. Systems deployed using affected versions of the registry container may allow a remote attacker to achieve root access with a blank password.	Registry