Technical impact
The Beta9 worker exposes a sandbox file API that incorrectly resolves container paths to host paths. The resolution logic allows a tenant to walk beyond the intended sandbox, enabling read, write, and delete operations on the worker's root filesystem as the container process runs with full privileges. The flaw can be leveraged to read sensitive files such as the Kubernetes service account token, which in the shipped manifests is bound to cluster‑admin. This capability to access arbitrary host files aligns with a high‑severity remote code execution risk where an attacker could potentially execute code on the host and compromise other tenants or the control plane.
Affected Systems
Beam‑Cloud’s Beta9 worker; tenants using a workspace token and a running sandbox are affected. The vulnerability is present in all releases prior to worker‑0.1.756. There is no version information beyond the upgrade target, so all earlier versions of the worker are at risk.
Risk and Exploitability
The CVSS score of 9.9 signals a critical security issue. The EPSS score is not available, but the lack of a KEV listing does not mitigate the severity, especially since the vulnerability impacts container isolation. The attack vector is inferred to be remote, via the API endpoints such as upload, download, and workspace sync, which are publicly reachable by authenticated tenants.