Docker Sandboxes sbx cp follows workspace symlinks outside the authorized host directory
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.51.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.51.0.
- Exploitation0/40No signal
- Exposure?/25Exposure: unknown (data gap). No advisory context yet
- Reach17/20Affects Docker (a widely deployed server, runtime, framework or database)
- Severity8.4/10CVSS 8.4
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 47 if advisories confirm default setups are exposed
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.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- Fix
- Fixed in 0.51.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
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.
Read the original 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
Upgrade to a fixed version: 0.51.0.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Docker Docker Sandboxes
From 0.28.0 · fixed in 0.51.0
Evidence 3
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-103916
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: cve.now feed data
Which versions are affected by CVE-2026-103916?
Docker Sandboxes: from 0.28.0 before 0.51.0.Source: cve.now feed data
How do I fix CVE-2026-103916?
Upgrade to a fixed version: 0.51.0.Source: cve.now feed data