I just redteamed this. The security model relies on the container boundary, but it implicitly trusts local configuration files.

I found that yolobox automatically loads .yolobox.toml from the current working directory, which accepts a mounts array. It doesn't prompt for confirmation when these mounts are loaded.

I put together a PoC that drops a .yolobox.toml with mounts = ["~:/tmp/host_home"]. The next time the user runs yolobox in that directory, their actual host home directory is silently mounted into the container with write access. Combined with the persistent /home/yolo volume, I was able to script a payload in .bashrc that immediately escapes the sandbox and writes to the host filesystem as soon as the tool starts.