High [CVE-2026-6406] The Docker CLI --use-api-socket flag bypasses Enhanced Container Isolation (ECI) restrictions in Docker Desktop
This high-severity Docker advisory covers CVE-2026-6406; related products: Docker Desktop, Docker Engine, Docker CLI.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Summary
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.
Is CVE-2026-6406 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-6406 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-6406?
The advisory VulniPulse tracks names no fixed release. Follow Docker's guidance for workarounds and updates.
Confirm against the vendor advisory before you patch.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.
Official advisory · medium-confidence parse· fetched 4 months ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists. Confirm against the vendor advisory.
Official advisory · medium-confidence parse· fetched 4 months ago·verify at source
Mitigation
The source record does not include mitigation steps. That does not mean no fix exists. Read the vendor advisory below for the authoritative guidance.
Official advisory · medium-confidence parse· fetched 4 months ago·verify at source
Get an email when Docker Desktop publishes the next one.
See Docker Desktop's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
More Docker advisories
- CVE-2026-17106Aug 18, 2026The tar extraction routines in moby/go-archive
- CVE-2026-112917Nov 3, 2026In Docker Desktop for Windows with the WSL2 backend, an unprivileged Linux container
- CVE-2026-114409Oct 27, 2026Docker Desktop before version 4.97.0 could write third-party API keys and OAuth access
- CVE-2026-106581Oct 9, 2026Before 4.92.0, Docker Desktop for Windows did not verify the signature of a package
- CVE-2026-92543Oct 7, 2026Docker Engine classifies a registry hostname as insecure using an any-match DNS check
- CVE-2026-92542Oct 7, 2026Docker: The firewall rules which mark VXLAN datagrams for encryption indiscriminately
iPhone and Android apps · New on the App Store
Monitor future Docker CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.