Menu

Docker's agent sandbox leaked through its copy command. Check every path that crosses the wall.
📰

Docker's agent sandbox leaked through its copy command. Check every path that crosses the wall.

DEV Community: docker·VOIR LABS·5 days ago
#ei9FcpU6
#devtodocker#devto#dev#path#copy
Reading 0:00
15s threshold

Originally published on voirlabs.io by Ijlal Ishaq.

A sandbox for an AI agent is only as strong as the least guarded way in or out of it. Docker Sandboxes put a coding agent in its own virtual machine and let it see only the folders you approve, and that part held. The gap was the copy command next to it. By the end of this article you will know why that keeps happening, and what a file channel that respects the boundary looks like in code.

The allowlist held. The copy command did not ask it.

Docker Sandboxes runs agents such as Claude Code, Codex and Gemini CLI inside a microVM with its own kernel, filesystem and network. You grant it specific folders, usually the project workspace, and those folders are shared into the VM. Together they form an allowlist: the only parts of your machine the agent is supposed to reach.

On November 3, Peyton Kennedy of Endor Labs published CVE-2026-103916, a flaw he found in sbx cp , the command that moves files between the sandbox and your machine.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.