EUVD-2026-79951
GHSA-wq46-97v9-q386
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture TOCTOU prevention
|
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 15, 2026
Docker Sandboxes 0.37.0 through 0.40.x contain a time-of-check/time-of-use race (CWE-367) in the guest-to-host Unix-domain socket relay: the host validates that a requested socket path sits inside an authorized workspace and then reconnects using that same pathname, letting a malicious guest swap an intermediate directory for a symlink in the gap. A guest that wins the race causes the host-side relay to connect to an arbitrary AF_UNIX socket outside the shared workspace, exposing whatever data or host capabilities that socket provides. Vendor-released fix: Docker Sandboxes 0.41.0; no public exploit code or CISA KEV entry was identified at time of analysis.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Know when Docker gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
Primary rating from Vendor (docker) · only source for this CVE.
CVSS VectorVendor: docker
Lifecycle Timeline
2DescriptionCVE.org
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.
Executive ViewAI
Docker Sandboxes versions 0.37.0 through 0.40.x contain a high-severity race condition (CVSS 8.7) that can allow code running inside a sandboxed guest to reach host-side Unix-domain sockets outside its authorized workspace, potentially exposing sensitive data or host-level capabilities. Any team relying on Docker Sandboxes for developer isolation or for containing untrusted workloads should treat this as a boundary-integrity issue, because the sandbox is the control that keeps guest activity away from host resources. A vendor fix is available in 0.41.0, and no public exploit code was identified at time of analysis, so exposure is manageable through prompt version upgrade.
Within 24 hours, inventory all installations of Docker Sandboxes and confirm which endpoints, developer workstations, CI runners, or build hosts are running versions 0.37.0 through 0.40.x; treat any host that runs untrusted or third-party guest images on those versions as potentially exposed and restrict or pause such workloads where operationally feasible. Within 7 days, upgrade every affected installation to Docker Sandboxes 0.41.0 (the vendor-released fix) and verify the running version post-upgrade, prioritizing hosts with access to sensitive sockets, orchestration control planes, or production credentials, and rotate any credentials or tokens that were reachable from a host socket on a system known to have run untrusted guests. Within 30 days, validate the remediation through configuration and version audits, add Docker Sandboxes version currency to your standard patch-management reporting, and review whether untrusted guest workloads can be constrained to hosts with minimal host-socket exposure to limit the blast radius of any future relay-layer flaws.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
An issue was discovered in Appsmith before 1.52. Rated critical severity (CVSS 9.8), this vulnerability is remotely expl
runc through version 1.0-rc6 (used in Docker before 18.09.2) contains a container escape vulnerability that allows attac
Netmaker makes networks with WireGuard. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no a
Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/
The News & Blog Designer Pack - WordPress Blog Plugin - (Blog Post Grid, Blog Post Slider, Blog Post Carousel, Blog Post
Path traversal in JFrog Artifactory (CWE-22) enables an authenticated low-privilege user to write data outside the inten
Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2) build
Remote code execution in Gogs through 0.14.2 allows authenticated users (and unauthenticated attackers on default-config
Unauthenticated remote command injection in SGWBOX N3 firmware 2.0.25 lets attackers execute arbitrary operating-system
Remote code execution in Flowise before 3.1.2 allows any authenticated user (or API caller with chatflow view/update per
Remote code execution in NocoBase Workflow Script Node (npm @nocobase/plugin-workflow-javascript) allows authenticated l
Docker Desktop Community Edition before 2.1.0.1 allows local users to gain privileges by placing a Trojan horse docker-c
Exploit-DB