Docker has released security fixes for two serious vulnerabilities in Docker Sandboxes that could allow a malicious guest environment to break workspace isolation and reach sensitive host-side resources.
The flaws, tracked as CVE-2026-77179 and CVE-2026-79994, were fixed in Docker Sandboxes version 0.42.0, released on September 7.
Docker Sandboxes isolate development agents, automated workflows, and untrusted workloads while allowing selective access to a host workspace.
Critical Docker Sandboxes Flaw
However, both newly disclosed issues stem from a time-of-check-to-time-of-use (TOCTOU) weakness involving filesystem path validation. In both cases, Docker Sandboxes validated that a requested pathname belonged to an approved shared workspace.
A malicious process inside the sandbox could then alter part of that path, such as by replacing a directory with a symbolic link, before the host performed the subsequent file or socket operation.
CVE-2026-77179 is the most severe issue and carries a Critical severity rating. It affects Docker Sandboxes versions 0.28.0 through versions prior to 0.42.0 on macOS.
The vulnerability exists in the macOS virtio-fs host server, which could incorrectly follow symbolic links when reopening an unlinked file using a previously stored path.
An attacker controlling code within a guest sandbox could race the host operation by replacing a parent directory after the original path had passed authorization checks. This could redirect a host-side file operation outside the intended shared directory.
According to Docker, successful exploitation may allow a malicious guest to read or modify arbitrary files that are accessible to the virtual machine monitor (VMM) user. In certain environments, that level of access could potentially be leveraged toward host code execution.
The risk is especially relevant to AI-assisted development and automated coding environments, where sandboxes may process untrusted repositories, generated scripts, third-party packages, or dependency installation routines.
The second issue, CVE-2026-79994, is rated High and affects Docker Sandboxes versions 0.37.0 through versions before 0.42.0. This vulnerability impacts the guest-to-host Unix domain socket relay.
While the relay initially confirmed that a requested socket path resided in an authorized workspace, it later connected using the original path string. A malicious guest could replace an intermediate directory with a symbolic link between validation and connection.
As a result, the host could be redirected to an arbitrary AF_UNIX socket outside the approved workspace.
Depending on the targeted local service, the flaw could expose sensitive data or enable unintended interactions with privileged host-side applications, developer tools, or platform services.
| CVE | Product / Component | Severity | Affected Versions | Security Impact | Fixed Version |
|---|---|---|---|---|---|
| CVE-2026-77179 | Docker Sandboxes virtio-fs host server on macOS | Critical | 0.28.0 to before 0.42.0 | Symlink race enables workspace escape, arbitrary VMM-user file read/write, and possible host code execution | 0.42.0 |
| CVE-2026-79994 | Docker Sandboxes guest-to-host Unix socket relay | High | 0.37.0 to before 0.42.0 | Symlink race can redirect host connections to unauthorized AF_UNIX sockets | 0.42.0 |
| CVE-2026-17106 | Docker Desktop docker container cp | Not stated | Before 4.86.0 | Destination-escape flaw | 4.86.0 |
| CVE-2026-5843 | Docker Model Runner MLX backend | Not stated | Before 4.71.0 | Container-to-host code execution | 4.71.0 |
| CVE-2026-5817 | Docker Model Runner vllm-metal backend | Not stated | Before 4.68.0 | Container-to-host code execution | 4.68.0 |
| CVE-2026-33990 | Docker Model Runner OCI Registry Client | Not stated | Before 4.67.0 | Server-side request forgery | 4.67.0 |
| CVE-2026-28400 | Docker Model Runner | Not stated | Before 4.62.0 | Runtime flag injection | 4.62.0 |
| CVE-2026-2664 | gRPC-FUSE kernel module | Not stated | Before 4.62.0 | Out-of-bounds read | 4.62.0 |
Organizations should immediately upgrade Docker Sandboxes to version 0.42.0 or later. Docker Sandboxes 0.43.0 also includes additional security hardening and workspace-related improvements. Until updates can be deployed, teams should use clone mode where possible and avoid read-write host mounts.
Security teams should minimize shared directories, keep credentials and sensitive repositories outside mounted workspaces, and treat sandboxes processing untrusted code as potentially hostile.
Join 16,000+ SOC teams using ANY.RUN to streamline threat investigations and reduce manual effort. Explore for your team