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 4 vulnerabilities in Docker Sandboxes with an average score of 5.9 out of ten.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 4 | 5.90 |
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 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.
