CVE-2026-103916
Docker Sandboxes sbx cp follows workspace symlinks outside the authorized host directory
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.
Fixes and workarounds
Fix
Upgrade Docker Sandboxes to version 0.51.0 or later.
Source: CNA: DockerWorkaround
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.
Source: CNA: DockerAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| Docker Sandboxes Docker Platforms: MacOS, Linux, Windows |
≥ 0.28.0; < 0.51.0 (affected, semver)
Other versions: unaffected |
CNA: Docker |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 8.4 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 | CNA: Docker |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://docs.docker.com/ai/sandboxes/CNA: Docker · product
- https://docs.docker.com/ai/sandboxes/security/isolation/CNA: Docker · technical-description
- https://github.com/docker/sbx-releases/releases/tag/v0.51.0CNA: Docker · release-notes
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.