Docker addressed two significant vulnerabilities in Docker Sandboxes, allowing a malicious guest workload to escape its designated shared workspace and access sensitive host-side resources This article explores vulnerabilities docker sandboxes. . The flaws, identified as CVE-2026-77179 and CVE-2026-79994, were resolved in Docker Sandboxes version 0.42.0, which was released on September 7.

Docker Sandboxes employs isolated microVM environments to run potentially untrusted workloads, including code and AI-agent tasks. Docker Sandboxes Vulnerabilities The affected component allows for symbolic links to be followed when reopening an unlinked file from a previously stored path. A successful exploit could allow a malicious guest to read or modify arbitrary files accessible to the Virtual Machine Monitor (VMM), potentially leading to workspace escape and compromise of the underlying macOS host.

It involves a guest-to-host Unix domain socket relay mechanism, enabling communication between the sandbox and authorized host-side Unix sockets. Organizations utilizing Docker Sandboxes should upgrade to version 0.42.0 or later, particularly for macOS users handling untrusted code, third-party repositories, or autonomous AI workloads. Docker recommends using clone mode and avoiding read-write host mounts when an immediate upgrade isn't feasible.

This pattern underscores the significance of promptly applying updates and minimizing host filesystem exposure in container- and microVM-based development workflows.