CVE-2026-103916
Docker Sandboxes sbx cp follows workspace symlinks outside the authorized host directory
- High 8.4
Description
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.
Key facts
- Published
- 3 Nov 2026
- Last changed
- 3 Nov 2026
- Assigned by
- Docker
- EPSS
- 0.21% likely to be exploited in the next 30 days, higher than 11.291% of CVEs (scores for 16 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 8.4CVSS 4.0, Highfrom the CNA (Docker)
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
What to do
- Upgrade Docker Sandboxes to version 0.51.0 or later.CNA solution statement
- Until upgrading, do not use sbx cp with a host-side source or destination inside a workspace writable by untrusted sandbox code. Use a host-only path for the copy instead.CNA workaround statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Docker | Docker Sandboxes |
|
Timeline
- 3 Nov 2026 Published