Docker Sandboxes Vulnerabilities: Critical Flaws

Introduction: Docker Sandboxes Vulnerabilities — Why It Matters

Docker Sandboxes Vulnerabilities include two security flaws that can weaken the isolation between an untrusted sandbox workload and the host system. Docker fixed the issues in Sandboxes 0.42.0, released on September 7, 2026. Docker identifies CVE-2026-77179 as Critical and CVE-2026-79994 as High.

The vulnerabilities involve unsafe path handling, symbolic links and time-of-check-to-time-of-use (TOCTOU) conditions. The most serious issue affects macOS installations and could allow a malicious guest to escape its intended shared workspace and access host files.

Organizations running untrusted repositories, third-party code or autonomous AI workloads should review their Docker Sandboxes versions and update affected installations.

What Are Docker Sandboxes?

Docker Sandboxes provide isolated environments for running workloads, including AI agents and other potentially untrusted code. The security model is designed to restrict what code running inside a sandbox can access on the host.

That isolation becomes especially important when a sandbox is used with external repositories or code that has not been fully reviewed. A vulnerability in the boundary between the guest and host can therefore increase the potential impact of a compromised or malicious workload.

Docker’s security advisory confirms that both vulnerabilities were addressed in Sandboxes 0.42.0.

What Caused the Docker Sandbox Security Issues?

The two vulnerabilities use different components but share a common security theme: unsafe filesystem path handling.

CVE-2026-77179 — Critical macOS Sandbox Escape

CVE-2026-77179 affects Docker Sandboxes on macOS from version 0.28.0 through versions before 0.42.0.

The flaw exists in the virtio-fs host server. Docker states that the component could follow symlinks when reopening an unlinked file from a stored path. A malicious guest could manipulate a parent directory and replace it with a symlink, potentially escaping the intended shared workspace.

The resulting access could allow arbitrary host files to be read or modified with the privileges of the VMM user. Docker also warns that host code execution could potentially follow from the issue.

CVE-2026-79994 — High-Severity Unix Socket Flaw

CVE-2026-79994 affects Docker Sandboxes versions 0.37.0 through versions before 0.42.0.

The guest-to-host Unix-domain socket relay first checks whether a socket path belongs to an authorized workspace. However, it subsequently reconnects using the pathname. A malicious guest could exploit that gap by replacing an intermediate directory with a symlink between the validation and connection steps.

This TOCTOU condition could cause the host to connect to an arbitrary AF_UNIX socket outside the authorized workspace, potentially exposing data or host-side capabilities provided through that socket.

Docker Sandboxes Vulnerabilities: Technical Breakdown

Timeline of Events

• September 7, 2026: Docker released Sandboxes 0.42.0 containing fixes for the two vulnerabilities.
• September 15, 2026: CVE records for the vulnerabilities were published.
• September 16, 2026: CERT-FR issued an advisory covering the Docker vulnerabilities and recommended applying the vendor fixes.

Affected Systems

The affected configurations include:

• Docker Sandboxes 0.28.0 to before 0.42.0 on macOS for CVE-2026-77179.
• Docker Sandboxes 0.37.0 to before 0.42.0 for CVE-2026-79994.
• Sandbox environments handling untrusted or potentially malicious workloads.
• Systems where host filesystem resources are exposed through shared or read-write mounts.

Docker recommends upgrading to 0.42.0 or later.

Potential Risks & Impact

Host File Access

The Docker Sandboxes Vulnerabilities could allow a malicious guest to move outside its intended workspace and read or modify host files accessible to the VMM user.

This makes host filesystem exposure an important factor when assessing the risk of vulnerable installations.

Host Code Execution

CVE-2026-77179 could potentially progress from unauthorized host file access to host code execution. This does not mean every vulnerable installation will result in code execution, but it demonstrates why sandbox-boundary vulnerabilities require prompt remediation.

Exposure of Host Capabilities

The Unix socket vulnerability could redirect connections toward unintended host-side sockets. Depending on the targeted socket, this could expose data or capabilities available through that interface.

Official Response and Fix

Docker addressed the Docker Sandboxes Vulnerabilities in Sandboxes 0.42.0. The vendor’s security advisory lists CVE-2026-77179 as Critical and CVE-2026-79994 as High and recommends upgrading.

The Docker Sandboxes security documentation provides additional information about sandbox isolation and security controls. The Docker release history also confirms that version 0.42.0 was released on September 7, 2026.

Industry Context: Why Sandbox Isolation Matters

Sandboxing is increasingly important as developers execute third-party repositories, automation scripts and AI-generated code. The security boundary must account not only for application-level permissions but also for filesystem paths, symbolic links, sockets and host interfaces.

Readers following broader cyber incident and vulnerability developments can also track how flaws in trusted infrastructure components can create security risks beyond the original application.

The Docker case demonstrates why isolation mechanisms themselves need regular security updates. Even when workloads are intentionally separated from the host, an implementation flaw can undermine that boundary.

How to Protect Yourself or Your Organization

1. Upgrade Docker Sandboxes: Move affected installations to version 0.42.0 or later.
2. Check macOS deployments: Review Sandboxes versions from 0.28.0 through 0.41.x for CVE-2026-77179.
3. Review older versions: Check installations from 0.37.0 through 0.41.x for CVE-2026-79994.
4. Use clone mode: Docker recommends clone mode when an immediate upgrade is not possible.
5. Avoid unnecessary read-write mounts: Minimize additional host filesystem exposure, particularly read-write mounts.
6. Audit untrusted workloads: Review repositories, scripts and AI workloads executed inside vulnerable sandboxes.
7. Limit host-side interfaces: Avoid exposing unnecessary host sockets or capabilities to sandboxed workloads.
8. Monitor security advisories: Follow Docker’s security announcements and apply future sandbox updates promptly.

For additional defensive guidance, organizations can review CyberNexora’s Learn & Protect resources and maintain an inventory of security-sensitive software components.

Key Takeaways

• Docker Sandboxes Vulnerabilities were fixed in version 0.42.0.
• CVE-2026-77179 is a Critical macOS issue involving symlink handling in virtio-fs.
• CVE-2026-79994 is a High-severity Unix socket relay issue involving a TOCTOU condition.
• Vulnerable sandbox configurations can increase exposure of host files or host-side capabilities.
• Docker recommends upgrading to 0.42.0 or later and using clone mode with limited host mounts when immediate upgrading is not possible.

Conclusion: Docker Sandboxes Vulnerabilities and What Happens Next

The Docker Sandboxes Vulnerabilities highlight the importance of protecting the boundary between isolated workloads and host systems. Filesystem paths, symlinks and host communication interfaces can become critical security boundaries when untrusted code is executed.

Administrators should verify their installed Sandboxes version, remove unnecessary host exposure and apply Docker’s security fixes. Readers can also follow CyberNexora’s latest cybersecurity updates for developments involving container, cloud and application security.