high8.4
CVE-2026-103916
Docker Sandboxes sbx cp does not safely confine host-side paths to a shared workspace. A...
Impact
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.
An attacker can exploit this with local access to the system, without logging in, but a user has to actively do something, such as open a file or a link. If it succeeds: high risk of data being read, high risk of data or systems being changed, high risk of outages.
Affected products · Docker
| Product | Affected versions |
|---|---|
| Docker Sandboxes | from 0.28.0 before 0.51.0 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://docs.docker.com/ai/sandboxes/
- https://docs.docker.com/ai/sandboxes/security/isolation/
- https://github.com/docker/sbx-releases/releases/tag/v0.51.0
- https://github.com/advisories/GHSA-82h2-77xp-45m9
- https://nvd.nist.gov/vuln/detail/CVE-2026-103916
- https://docs.docker.com/ai/sandboxes
- https://docs.docker.com/ai/sandboxes/security/isolation