Severity by source
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Local access inside sandbox (AV:L), low privileges (PR:L), scope change (S:C) because write escapes to host; no confidentiality or availability impact.
Primary rating from Vendor (Docker).
CVSS VectorVendor: Docker
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
1DescriptionCVE.org
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.
AnalysisAI
Docker Sandboxes (sbx) fails to enforce read-only semantics on virtio-fs host mounts: the in-guest bind correctly receives the read-only flag, but the underlying host-edge grant omitted from the policy-share allowlist carries no access mode, leaving the shared-export path fully writable at the host level. Low-privileged code executing inside the sandbox can enumerate or derive the virtio-fs export path and write to host directories the operator explicitly attached as read-only, breaking the isolation guarantee that is the product's core security promise. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires that the attacker already has unprivileged code execution inside the Docker Sandbox (sbx) guest environment - this is the product's intended operating model for running untrusted workloads, so this condition is expected to be met in targeted deployments. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The supplied CVSS 4.0 base score of 5.7 (Medium) reflects AV:L and PR:L - an attacker must already have low-privileged code execution inside the sandbox, materially limiting the attack surface to workloads that intentionally run untrusted or semi-trusted code inside sbx environments, which is the product's stated use case. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker with low-privileged code execution inside a Docker Sandbox - for example, a malicious or compromised AI workload running in the sbx environment - enumerates or derives the virtio-fs shared-export path for a host directory the operator mounted as read-only. Because the host-edge grant carries no access mode restriction, the attacker writes arbitrary data to that host path, potentially overwriting configuration files, injecting content into shared data directories, or tampering with artifacts that other host processes will subsequently consume. … |
| Remediation | No vendor-released patch version has been independently confirmed from the available data - the references point to product documentation rather than a security advisory. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
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
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
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
Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to version 25.2.169 and Application prior to version 2
An issue in Plone Docker Official Image 5.2.13 (5221) open-source software that could allow for remote code execution du
Same weakness CWE-863 – Incorrect Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-57236
GHSA-q3q4-c92f-m955