CVE
CubeSandbox host filesystem access via unrestricted bind mounts
Affects CubeSandbox versions before 0.5.1 where a caller permitted to create sandboxes supplies the Cube-specific host-mount metadata option. Fixed in 0.5.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- Exploited
- No known exploitation
- Fix
- Fixed in 0.5.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. CubeSandbox versions before 0.5.1 The caller must be permitted to create a sandbox The host-mount sandbox metadata option is used to supply the host path
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
CubeSandbox from TencentCloud lets any authenticated tenant who can call the sandbox-create API remotely mount arbitrary host directories into their MicroVM, read-write by default. An attacker can use this to read and modify files on the host, run code on the host, reach the container runtime, and compromise other tenants on the same system.
Original description
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.
Who should check
Operators of multi-tenant CubeSandbox deployments below 0.5.1 where tenants can call POST /sandboxes to create sandboxes
“Affected versions <0.5.1”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.4, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
CubeSandbox versions before 0.5.1 The caller must be permitted to create a sandbox The host-mount sandbox metadata option is used to supply the host pathUpgrade to a fixed version: 0.5.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-120699 (CubeSandbox: Unrestricted host-directory bind-mount: any sandbox-create caller mounts arbitrary host paths (RW) into their MicroVM), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-120699 (entry last updated 2026-11-16):
Affected:
- TencentCloud CubeSandbox: fixed in 0.5.1
Fixed versions: 0.5.1.
Conditions (all must be true for the bug to be hit):
- CubeSandbox versions before 0.5.1 (source: https://github.com/TencentCloud/CubeSandbox/security/advisories/GHSA-8frp-jfpv-5vhv)
- The caller must be permitted to create a sandbox (source: https://github.com/TencentCloud/CubeSandbox/security/advisories/GHSA-8frp-jfpv-5vhv)
- The host-mount sandbox metadata option is used to supply the host path (source: https://github.com/TencentCloud/CubeSandbox/security/advisories/GHSA-8frp-jfpv-5vhv)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-120699 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120699 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/TencentCloud/CubeSandbox/security/advisories/GHSA-8frp-jfpv-5vhv
- https://github.com/TencentCloud/CubeSandbox/pull/756
- https://github.com/TencentCloud/CubeSandbox/commit/5c7025f3a393c30e723dd7f071ef1c28d7a2e52e
- https://github.com/TencentCloud/CubeSandbox/releases/tag/v0.5.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-120699
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120699"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- TencentCloud CubeSandbox
fixed in 0.5.1
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120699
Is CVE-2026-120699 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Any caller permitted to create a sandbox can bind-mount an arbitrary host path read-write into their MicroVM. The advisory says this gives host-root file read and write, host remote code execution, access to the container runtime, and compromise of other sandboxes on the node.Source: github.com
Which versions are affected by CVE-2026-120699?
CubeSandbox: before 0.5.1.Source: cve.now feed data
Am I affected, and how do I check?
CubeSandbox versions before 0.5.1 are affected. The issue involves the host-mount metadata option that supplies the host path when a sandbox is created, so check the installed CubeSandbox version against 0.5.1 and whether sandbox creation uses that option.Source: github.com
How do I fix CVE-2026-120699?
Upgrade CubeSandbox to 0.5.1 or later, the fixed version.Source: github.com