Is CVE-2026-103916 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-103916 being exploited in the wild.

How severe is CVE-2026-103916?

Informational severity, published 3 November 2026.

Is there a fix for CVE-2026-103916?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-103916 attacked?

It is attacked with local access, in a hosted service.

Am I affected by CVE-2026-103916?

Check whether you run Docker Sandboxes. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-103916: Docker Sandboxes sbx cp path traversal via symlink

CVE-2026-103916 · Severity: info · Published 2026-11-03

Docker Sandboxes is a feature that allows running isolated containerized workloads with controlled resource sharing. A malicious sandbox can exploit the sbx cp command to create symlinks that allow reading files from the host system outside the intended workspace, or writing malicious data to arbitrary host locations with the permissions of the invoking user.

Technologies: Docker Sandboxes. Vendors: Docker.

Quick answers

Is CVE-2026-103916 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-103916 being exploited in the wild.
How severe is CVE-2026-103916?: Informational severity, published 3 November 2026.
Which products and versions are affected?: Docker Sandboxes.
Is there a fix for CVE-2026-103916?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-103916 attacked?: It is attacked with local access, in a hosted service.
Am I affected by CVE-2026-103916?: Check whether you run Docker Sandboxes. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The sbx cp command fails to safely validate host-side paths before following symlinks in shared workspace directories. A malicious sandbox can preemptively create or replace workspace symlinks, causing subsequent user-initiated copy operations to read host files outside the workspace into the sandbox or write sandbox-controlled data to host paths outside the workspace. This is a symlink-based directory traversal vulnerability requiring the sandbox to have filesystem access to the shared workspace.

Affected products

Docker Sandboxes

Timeline

2026-11-03: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.