The vulnerability arises from incorrect authorization in Docker Desktop's handling of socket mounts when using the --use-api-socket flag. Enhanced Container Isolation (ECI) is designed to block Docker socket mounts from containers unless explicitly allowed via admin settings. However, the --use-api-socket flag mounts the Docker socket via HostConfig.Mounts instead of HostConfig.Binds. Since the ECI enforcement inspects only the Binds field, this mount bypasses the restriction, granting the container full access to the Docker Engine socket and any stored authentication credentials. This enables a local attacker with Docker CLI command execution to escape ECI confinement and potentially escalate privileges on the host.

Exploitation allows a local attacker with Docker CLI access to bypass Enhanced Container Isolation, gaining full access to the Docker Engine socket. This can lead to unauthorized control over Docker containers and the host system, including access to container registry credentials if the host user is logged in. The vulnerability has a CVSS 4.0 score of 8.8, indicating high impact on confidentiality, integrity, and availability.

Patch status is not yet confirmed — check the Docker vendor advisory for current remediation guidance. Until an official fix is available, restrict local user access to Docker CLI commands and avoid enabling the --use-api-socket flag in environments requiring strict container isolation. Monitor Docker's official channels for updates and apply patches promptly once released.