Endor Labs found that a separate copy channel could follow a workspace symlink outside approved host paths. The shared-filesystem allowlist held; a later operator copy triggered the access.
THE CONTROL LESSON
What should we watch for?
Ackuity’s view: validate the resolved source and destination of each file action outside the agent’s control, before it runs.
THE EVIDENCE
What does the report establish?
The finding concerns the standalone Docker Sandboxes sbx CLI, not Docker Desktop. Planting a symlink alone did not access the host; a later operator copy was required. Canary read/write tests do not establish exploitation in the wild or demonstrated code execution. November 3 is the disclosure and fix date.
Read the full account
Endor Labs demonstrated host-file reads and overwrites through sbx cp. Docker’s v0.51.0 release blocks workspace symlink escapes.
A shared-filesystem restriction does not automatically govern a separate copy channel.
ORIGINAL REPORTING & EVIDENCE