Docker Sandboxes macOS Host Filesystem Escape (CVE-2026-77179)
First seen Sep 18, 2026 · Updated Sep 18, 2026
A critical vulnerability in Docker Sandboxes on macOS allows malicious code running inside a sandboxed virtual machine to break out of its designated project directory and read or modify arbitrary files on the host system. The escape executes with the privileges of the host user account running the VM, enabling data theft, tampering, or further compromise of the host machine.
Technical Analysis
CVE-2026-77179 is a sandbox escape vulnerability in Docker Sandboxes affecting macOS, allowing guest code within the virtualized environment to traverse outside the shared project directory and access the broader host filesystem. Because the escaped process inherits the permissions of the host account running the VM, an attacker could read sensitive files, modify configuration or source code, or plant persistence mechanisms without additional privilege escalation. Docker rated the issue Critical, indicating high exploitability and severe impact given how commonly these sandboxes are used for isolating untrusted or third-party code during development and testing. This flaw is particularly concerning for AI agent development workflows, where autonomous coding agents or AI-driven CI/CD pipelines often execute untrusted, LLM-generated, or third-party code inside Docker-based sandboxes for isolation; a successful escape could let malicious or hallucinated agent-generated code exfiltrate API keys, model credentials, or proprietary data from the host machine running the agent orchestration layer.
Affected Systems
Docker Sandboxes running on macOS hosts; specific affected version ranges as detailed in Docker's official security announcement (September 15, 2026 advisory)
Indicators of Compromise
- No specific IOCs published; vulnerability disclosed via Docker's official security advisory (CVE-2026-77179)
Remediation Steps
- 1
Apply Vendor Patch
Update Docker Desktop/Docker Sandboxes to the patched version specified in Docker's official security advisory as soon as it is available.
- 2
Restrict Untrusted Code Execution
Avoid running untrusted, third-party, or AI-agent-generated code inside Docker Sandboxes on macOS until patched, especially in environments where agents autonomously execute generated code.
- 3
Audit Host Permissions
Review and minimize the privileges of the host user account used to run Docker Sandboxes VMs to limit the blast radius of a potential escape.
- 4
Monitor File Integrity
Implement host-based file integrity monitoring to detect unauthorized modifications outside the expected sandbox project directory.
- 5
Isolate Agent Workflows
For AI agent pipelines using Docker for code execution isolation, consider additional layers of sandboxing (e.g., microVMs, gVisor) until the Docker fix is confirmed and deployed.
CVE / Advisory IDs
Industries Most Exposed
Respond to this threat
Pro subscribers get a full AI-generated incident-response playbook for this threat — detection, containment, eradication, and recovery steps — plus an unlimited AI Threat Advisor for questions about your environment.