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.
0.4% estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-22Improper Limitation of a Pathname to a Restricted Directory (Path traversal) CWE-269Improper Privilege Management CWE-284Improper Access Control
Show the promptExplain CVE-2026-120699 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120699?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120699?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-120699 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.