Docker Sandboxes Docker Sandboxes

Don't miss out!

Thousands of developers use stack.watch to stay informed.
Get an email whenever new security vulnerabilities are reported in Docker Sandboxes.

By the Year

In 2026 there have been 12 vulnerabilities in Docker Sandboxes with an average score of 6.6 out of ten.

Year Vulnerabilities Average Score
2026 12 6.63

It may take a day or so for new Docker Sandboxes vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Docker Sandboxes Security Vulnerabilities

Docker sandboxd privilege escalation via unsafe HOME/XDG_STATE_HOME (0.53.0)
CVE-2026-126329 7.3 - High - November 12, 2026

Docker Sandboxes reuses existing state and configuration directories without verifying their ownership. If sbx or sandboxd is run as root with HOME or, on Linux, XDG_STATE_HOME pointing to an attacker-controlled location, a local unprivileged user can substitute control-plane sockets and configuration trusted by the root process, potentially executing commands as root. Exploitation requires a privileged invocation with an attacker-influenced environment. The issue affects Linux and macOS and is fixed in version 0.53.0.

Improper Ownership Management

Docker Engine sandbox port-binding republish vulnerability (fixed in 0.53.0)
CVE-2026-126330 2.4 - Low - November 12, 2026

Docker Sandboxes can silently republish a sandbox service after an operator removes its automatically assigned host-port mapping. The daemon removes the active binding but retains the original publication request, allowing a later port change or sandbox restart to publish the service again on a new host port. An attacker able to reach the restored endpoint may regain access to the service. Both TCP and UDP mappings are affected. Exposure is limited to the original bind address, which defaults to loopback. The issue is fixed in version 0.53.0.

Operation on a Resource after Expiration or Release

Docker Sandboxes RCE via Git config injection < 0.50.0
CVE-2026-121614 7.1 - High - November 03, 2026

Docker Sandboxes versions 0.31.0 before 0.50.0 do not neutralize repository-controlled Git configuration when running certain host-side Git commands. An attacker who can modify a host repository's Git configuration, for example through a direct-mode sandbox with the repository mounted read-write, can configure core.fsmonitor or another Git setting that invokes an external program. Git can execute the program during a later clone-mode fetch or, starting in version 0.39.0, an sbx kit push initiated by the user. The program runs on the host with the invoking user's permissions, outside the sandbox's microVM isolation. The read-only host repository mount provided to a clone-mode sandbox does not itself allow that sandbox to modify the host repository's Git configuration. The issue is fixed in version 0.50.0.

External Control of System or Configuration Setting

Docker sbx cp Host Path Escalation via Symlink Attack
CVE-2026-103916 8.4 - High - November 03, 2026

Docker Sandboxes sbx cp does not safely confine host-side paths to a shared workspace. A malicious sandbox can create or replace a workspace symlink so that a later user-initiated copy reads a host file outside the workspace into the sandbox or writes sandbox-controlled data to a host path outside the workspace with the invoking user's permissions.

insecure temporary file

Docker Sandbox Credential Forwarding Flaw (CVE-2026-105452)
CVE-2026-105452 5.9 - Medium - October 08, 2026

Docker Sandboxes could forward a client-supplied credential alongside a credential injected by the host egress proxy. The proxy removed alternate credentials only when their values matched known sentinel values, so untrusted code in an authorized sandbox could supply an unrecognized credential in another supported authentication header. For affected upstream services, this could authenticate the request to an attacker-controlled account and expose data included in the request.

Information Disclosure

Docker Sandbox OAuth Hostname Case Sensitivity Bypass
CVE-2026-105570 6.7 - Medium - October 08, 2026

Docker Sandboxes compared OAuth token-endpoint hostnames case-sensitively when deciding whether to mask managed credential responses, while request routing treated DNS hostnames case-insensitively. Untrusted code inside a sandbox could use a case-variant hostname to reach the genuine provider endpoint while bypassing response masking. If a user completed the OAuth flow, the provider's access and refresh tokens could be returned unmasked to the sandbox, exposing host-managed credentials.

Improper Handling of Case Sensitivity

Docker Sandbox Unix-Domain Socket Relay Symlink Validation Bypass
CVE-2026-79994 8.7 - High - September 15, 2026

The guest-to-host Unix-domain socket relay in Docker Sandboxes validates that a socket path is inside an authorized workspace, but later reconnects using the pathname. A malicious guest can replace an intermediate directory with a symlink between validation and connection, causing the host to connect to an arbitrary AF_UNIX socket outside the shared workspace. This can expose data or host-side capabilities provided by the targeted socket.

TOCTTOU

Docker virtio-fs Symlink Traversal on macOS Host
CVE-2026-77179 9.4 - Critical - September 15, 2026

On macOS, the virtio-fs host server used by Docker Sandboxes improperly follows symlinks when reopening an unlinked file from a stored path. A malicious guest can replace a parent directory with a symlink, escape the shared workspace, and read or modify arbitrary host files as the VMM user, potentially achieving host code execution.

insecure temporary file

Docker go-archive Untrusted Extraction Enables Arbitrary File Overwrite (CVE-2026-17106)
CVE-2026-17106 7.1 - High - August 18, 2026

The tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the ApplyLayer helpers) do not confine filesystem operations to the destination directory. The extractor decides where each archive entry lands using lexical string checks and then performs the filesystem operation on a path that is resolved by the OS, so links introduced by the archive can be followed out of the destination directory. An attacker who controls the contents of an archive can create or overwrite files at arbitrary paths writable by the extracting process.

insecure temporary file

Docker Sandbox virtiofs readonly intent bypass
CVE-2026-18171 5.7 - Medium - August 12, 2026

Docker Sandboxes (sbx) applies the read-only intent of a runtime host mount to the in-guest container bind only: the underlying virtio-fs host-edge grant is added to the sandbox's policy-share allowlist with no access mode. The directory stays writable at its shared-export path, so unprivileged code inside the sandbox can derive that path and write to a host directory the operator attached read-only.

AuthZ

Docker Sandbox ICMP Egress Bypass Through Daemon Restart
CVE-2026-12539 5.1 - Medium - June 18, 2026

Docker Sandboxes (sbx) blocks ICMP egress with an authorizer applied only at network-creation time, and does not re-apply it to networks rebuilt from disk when the Docker daemon restarts, so a restart-surviving sandbox forwards ICMP to arbitrary hosts. A workload inside a sandbox, which the threat model treats as untrusted, can therefore defeat the documented ICMP egress block to perform network reconnaissance and exfiltrate data over an ICMP covert channel, regardless of the configured allowlist.

Improper Restriction of Communication Channel to Intended Endpoints

Docker Sandbox DNS Exfil via Resolver Bypass
CVE-2026-12039 5.7 - Medium - June 18, 2026

Docker Sandboxes (sbx) enforces an HTTP/S-only egress allowlist but does not apply it to DNS resolution: the per-network embedded DNS server forwards any queried name to the host resolver whenever the network is internet-connected, without consulting the policy. A workload inside a sandbox, which the threat model treats as untrusted, can therefore encode data into DNS labels for an attacker-controlled domain and exfiltrate it through a DNS covert channel, bypassing the configured allowlist.

Improper Restriction of Communication Channel to Intended Endpoints

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Docker Sandboxes or by Docker? Click the Watch button to subscribe.

Docker
Vendor

subscribe