CVE-2026-120699: CubeSandbox: Unrestricted host-directory bind-mount: any sandbox-create caller mounts arbitrary host paths (RW) into their MicroVM
CubeSandbox is an instant, concurrent, secure, and lightweight sandbox for AI agents. Prior to 0.5.1, any authenticated tenant permitted to call POST /sandboxes can supply metadata["host-mount"] with an arbitrary existing host path because the control plane performs no authorization check or allowed-prefix validation for the path. injectHostDirMounts forwards the path to prepareHostDirVolume, where Cubelet uses mount --rbind through the function to perform a recursive bind mount as root and exposes the host subtree to the tenant's MicroVM through virtio-fs, read-write by default. This allows host-root file access and modification, host code execution, access to the container runtime, and compromise of co-resident tenants without a kernel or virtual-machine-monitor flaw. This issue is fixed in version 0.5.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.5.1
Event History
Frequently Asked Questions
Who can exploit this issue?
Any authenticated tenant that is permitted to call POST /sandboxes can exploit it. No kernel or virtual-machine-monitor vulnerability is required.
What access does an attacker need?
The attacker needs permission to create a sandbox and must provide an arbitrary existing host path in metadata["host-mount"]. The control plane does not authorize that path or restrict it to approved prefixes.
Are mounted host directories writable from the sandbox?
Yes. The recursive host bind mount is exposed to the tenant's MicroVM through virtio-fs and is read-write by default, allowing modification of the mounted host subtree.
What is the potential impact?
An attacker can access and modify host-root files, potentially execute code on the host, access the container runtime, and compromise co-resident tenants.
Which versions are affected?
Versions prior to 0.5.1 are affected. The issue is fixed in version 0.5.1.