You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
The Docker CLI --use-api-socket flag bypasses Enhanced Container Isolation (ECI) restrictions in Docker Desktop. When ECI is enabled, Docker socket mounts from containers are denied unless explicitly allowed via the admin-settings configuration. However, the --use-api-socket flag adds the Docker socket mount via the HostConfig.Mounts field rather than the HostConfig.Binds field. The ECI enforcement in the Docker Desktop API proxy only inspected Binds, allowing the mount to pass unchecked. This grants a container full access to the Docker Engine socket and, if the host user has logged in to container registries, their authentication credentials.
A local attacker with the ability to run Docker CLI commands can exploit this to escape ECI restrictions, access the Docker Engine, and potentially escalate privileges.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
Title: Docker Desktop de Docker, Description: La bandera '--use-api-socket' de Docker CLI elude las restricciones de Aislamiento Mejorado de Contenedores (ECI) en Docker Desktop. Cuando ECI está habilitado, los montajes de sockets de Docker desde los contenedores son denegados a menos que se permitan explícitamente a través de la configuración de admin-settings . Sin embargo, la bandera '--use-api-socket' añade el montaje del socket de Docker a través del campo 'HostConfig.Mounts' en lugar del campo 'HostConfig.Binds'. La aplicación de ECI en el proxy de la API de Docker Desktop solo inspeccionaba Binds , permitiendo que el montaje pasara sin ser verificado. Esto otorga a un contenedor acceso completo al socket del Docker Engine y, si el usuario del host ha iniciado sesión en registros de contenedores, sus credenciales de autenticación.
Un atacante local con la capacidad de ejecutar comandos de Docker CLI puede explotar esto para evadir las restricciones de ECI, acceder al Docker Engine y potencialmente escalar privilegios.
AND
OR
*cpe:2.3:a:docker:docker_desktop:*:*:*:*:*:*:*:* versions from (including) 4.41.0 up to (excluding) 4.59.0
OR
cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*
cpe:2.3:o:apple:macos:-:*:*:*:*:*:*:*
Docker Inc.: https://www.zerodayinitiative.com/advisories/ZDI-26-299/ Types: Third Party Advisory
New CVE Received from Docker Inc.5/22/2026 3:17:04 PM
Action
Type
Old Value
New Value
Added
Description
The Docker CLI --use-api-socket flag bypasses Enhanced Container Isolation (ECI) restrictions in Docker Desktop. When ECI is enabled, Docker socket mounts from containers are denied unless explicitly allowed via the admin-settings configuration. However, the --use-api-socket flag adds the Docker socket mount via the HostConfig.Mounts field rather than the HostConfig.Binds field. The ECI enforcement in the Docker Desktop API proxy only inspected Binds, allowing the mount to pass unchecked. This grants a container full access to the Docker Engine socket and, if the host user has logged in to container registries, their authentication credentials.
A local attacker with the ability to run Docker CLI commands can exploit this to escape ECI restrictions, access the Docker Engine, and potentially escalate privileges.