CVE-2026-103916: Docker Sandboxes sbx cp follows workspace symlinks outside the authorized host directory
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-04 15:41 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by Docker, published 2026-11-03).
Weakness: CWE-59: Improper Link Resolution Before File Access (‘Link Following’)
How it can be exploited
Exploitable with local access with low attack complexity with no special attack requirements needing no privileges and a user must actively take an action. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer found 1 research write-up naming this CVE.
See all 3 references on Exploit Observer
Live scores
- EPSS
- 0.002
low predicted chance of attack - VEDAS
- 0.048
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Docker Sandboxes | from 0.28.0 before 0.51.0 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 0.51.0.
Vendor guidance:
- https://github.com/docker/sbx-releases/releases/tag/v0.51.0 (release-notes)
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
Advisories on this CVE
References
Vendor advisories and patches
- https://github.com/docker/sbx-releases/releases/tag/v0.51.0 (release-notes)
Technical analysis and advisories
- https://docs.docker.com/ai/sandboxes/security/isolation/ (technical-description)
Other references
- https://docs.docker.com/ai/sandboxes/ (product)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
