CVE-2026-6406: Docker Desktop Enhanced Container Isolation bypass via API socket flag

CVE-2026-6406 · Severity: high · CVSS 8.8 · Published 2026-05-22

A security flaw in Docker Desktop allows users to bypass 'Enhanced Container Isolation' (ECI) protections. This feature is intended to restrict containers from accessing the underlying host system's Docker engine. By exploiting this bypass, a local user or a compromised container can gain full control over the Docker environment and potentially access sensitive authentication credentials stored on the host.

Quick answers

Is CVE-2026-6406 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-6406 being exploited in the wild.
How severe is CVE-2026-6406?
High severity, with a CVSS score of 8.8, published 22 May 2026.
Which products and versions are affected?
Docker Docker Desktop 4.41.0 to 4.58.x (fixed in 4.59.0).
Is there a fix for CVE-2026-6406?
A patch was published on 2026-04-23: Coordinated public release of advisory and fix in 4.59.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-6406 attacked?
It is attacked with local access, in a network appliance.
Am I affected by CVE-2026-6406?
Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability in the Docker Desktop API proxy allows a bypass of Enhanced Container Isolation (ECI) when the --use-api-socket flag is used. ECI is designed to block Docker socket mounts unless explicitly permitted; however, the enforcement mechanism only inspected the 'HostConfig.Binds' field. The --use-api-socket flag utilizes the 'HostConfig.Mounts' field instead, which was not validated by the proxy. A local attacker with low-privileged access can exploit this to mount the Docker Engine socket, escaping container isolation and potentially escalating privileges or stealing host-level registry credentials. The issue is fixed in Docker Desktop version 4.59.0.

Affected products

  • Docker Docker Desktop 4.41.0 to 4.58.x (fixed in 4.59.0)

Timeline

  • 2026-01-09: other: Vulnerability reported to vendor
  • 2026-04-23: patched: Coordinated public release of advisory and fix in 4.59.0
  • 2026-05-22: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.