Technical impact
An attacker who controls a Beta9 workspace can attach a volume when deploying code. The gateway concatenates the shared volumes root, the workspace name, and the supplied volume identifier to build a host path. Because the identifier is not validated against the workspace’s ownership or sanitized to remove parent‑directory segments, an attacker can supply a path like "../" that resolves outside the intended volume directory. The worker then bind‑mounts this path into the sandbox with read‑write permissions unless the volume was marked read‑only, giving the tenant full read and write access to files on the worker’s host filesystem, including other tenants’ data.
Affected Systems
The flaw exists in beam‑cloud Beta9 gateway versions prior to 0.1.776 and beta‑9 worker versions prior to 0.1.756. The issue was confirmed against gateway 0.1.769 and worker 0.1.745, and it is fixed in gateway 0.1.776 and worker 0.1.756.
Risk and Exploitability
The CVSS score is 9.9, indicating critical severity. The EPSS score is not available, but a standard workspace token is sufficient for exploitation, so the likelihood of real‑world attacks is high in environments that expose the API to untrusted tenants. The vulnerability is not listed in the CISA KEV catalog.