Loading story…
Docker disclosed and fixed CVE-2026-79994, a high-severity time-of-check to time-of-use (TOCTOU) vulnerability in the host-side relay used by Docker Sandboxes. A malicious sandbox guest could alter an intermediate workspace directory after validation of a Unix-socket path, replacing it with a symbolic link and causing the trusted relay to connect to an AF_UNIX socket outside the approved workspace.
The flaw affects Docker Sandboxes versions 0.37.0 through versions before 0.41.0; version 0.41.0 includes the specific fix. Docker's broader security advisory recommends upgrading deployments to 0.43.0 or later. Although the issue does not directly grant unrestricted host filesystem access, it can enable a guest to influence connections to reachable host socket services, potentially affecting confidentiality and integrity; no active exploitation has been confirmed.
See real exploitation activity before you spend the cycle.
2 events from the most recent confirmed update back to the earliest known activity.
Docker published a security advisory concerning vulnerabilities affecting Docker Sandboxes releases earlier than version 0.43.0. The advisory recommended upgrading affected deployments, without providing CVE identifiers, severity ratings, technical details, or evidence of exploitation.
Docker fixed high-severity CVE-2026-79994 in the Docker Sandboxes host-side relay. The TOCTOU flaw affected versions 0.37.0 through versions before 0.41.0 and could let a malicious guest redirect the relay to an arbitrary reachable pathname-based Unix socket; version 0.41.0 contains the fix, and no active exploitation was confirmed.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
3 references tracked. Mallory keeps watching after this page renders.
linuxsecurity.com
Open sourcecirt.gy
Open sourcedocs.docker.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A vulnerability in **Docker Sandboxes** allowed code running inside a sandbox to bypass a read-only mount and modify host files through an alternate writable path, creating a path for tampering with source code, CI configuration, infrastructure-as-code, and other build inputs that could later execute on the host or in CI pipelines. The flaw, tracked as **`CVE-2026-18171`** with a **CVSS 5.7** score, affected versions **`0.35.0` through `0.38.0`** across **macOS, Linux, and Windows**. The issue stemmed from the same host directory being exposed twice: as a read-only **VirtioFS** mount at a user-specified path and as a writable Docker host export under **`/mnt/host`**. Researchers demonstrated exploitation on **Windows 11** using PowerShell, showing that a compromised coding agent or attacker-controlled code inside the sandbox could write to files that users expected to be protected. Docker reproduced the behavior, fixed the vulnerability, and released a patch on **August 12, 2026**.
Aug 13, 2026
A security flaw in **Tecnativa `docker-socket-proxy`** allows unintended read access to container data when the proxy is configured with `CONTAINERS=1`, even if `POST=0` is set. Public reports and a proof of concept show that the proxy's HAProxy rules broadly permit the Docker API `/containers/*` namespace, enabling an attacker with access behind the proxy to list containers and reach sensitive GET endpoints that were not meant to be exposed. The exposed endpoints reportedly include `/archive`, `/export`, `/logs`, and `/top`, which can be used to read arbitrary files from containers, export full container filesystems, inspect process arguments, and retrieve logs. An open issue states there is no built-in mitigation short of manually editing the HAProxy configuration, while a linked pull request proposes restricting filesystem-related exposure through more granular controls such as `ALLOW_ARCHIVE`, `ALLOW_EXPORT`, and `ALLOW_LOGS` and corresponding HAProxy configuration changes.
Aug 23, 2026
Imperva disclosed **CopyEscape**, tracked as `CVE-2026-17106`, a container-to-host arbitrary file-write vulnerability in Docker’s `docker cp` functionality that allows a malicious container to create or overwrite files outside the destination chosen by the user on the machine running the Docker CLI. The issue stems from a filesystem race in Docker’s archive creation path combined with unsafe symlink handling during extraction, turning a routine file copy from a container into a host write primitive. Docker confirmed the same CVE also affects `sbx cp` in Docker Sandboxes when copying files out of sandboxes. Imperva said exploitation was validated against Docker Engine `29.6.1` on Linux and Docker Desktop `4.81.0` on macOS, with impact ranging from compromise of the developer account using the CLI to **root code execution** when `docker cp` is run with elevated privileges. Fixes are available in Docker Engine and CLI `29.7.2` or later, Docker Desktop `4.86.0` or later, and Docker Sandboxes `0.38.0` or later.
Aug 12, 2026