CVE-2026-120308

Beta9 host filesystem exposure via volume path traversal

Published Nov 1, 2026 CVSS 3.1 · 9.9 Critical EPSS < 1% KEV · Not listed
Description
A Beta9 tenant can attach a volume when deploying a function, endpoint, or task queue. The gateway builds the host path by joining the shared volumes root, the workspace name, and the volume identifier from the stub configuration. Nothing checks that the identifier names a volume that workspace owns. Parent-directory segments in the identifier collapse the joined path to the worker's filesystem root, and the worker bind-mounts that path into the sandbox read-write unless the volume was explicitly marked read-only. A tenant with a workspace token can therefore read and write the worker's files, including other tenants' volumes stored on that machine. Confirmed against gateway 0.1.769 and worker 0.1.745. Fixed in gateway 0.1.776 and worker 0.1.756: volume identifiers and mount paths are validated before a mount is built, including for stubs saved before the check existed, and the gateway rejects a volume that does not exist or is not owned by the workspace.

Analysis

AI-generated

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.

Remediation

Vendor Solution

Upgrade the gateway to 0.1.776 or later and the worker to 0.1.756 or later. Volume identifiers and mount paths are rejected when they are empty, ".", "..", or contain a slash (identifiers) or a ".." segment (mount paths). The gateway also refuses a volume the workspace does not own. Stubs stored before the check existed are validated when they are launched. The fix is commit a28bf12 (pull request 1897), released on 2026-09-15.


OpenCVE Recommended Actions

  • Upgrade the gateway to 0.1.776 or later and the worker to 0.1.756 or later, making sure all deployments use these patched versions.
  • Validate volume identifiers to reject empty strings, '.', '..', and any slash characters, and enforce that the identifier belongs to the workspace that is executing the function before creating the mount.
  • Rotate or revoke any workspace tokens that were in use before the patch, and monitor system logs for attempts to mount unauthorized paths.

Generated by OpenCVE AI on November 1, 2026 at 14:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Beam-cloud
Beam-cloud beta9
Vendors & Products Beam-cloud
Beam-cloud beta9
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description A Beta9 tenant can attach a volume when deploying a function, endpoint, or task queue. The gateway builds the host path by joining the shared volumes root, the workspace name, and the volume identifier from the stub configuration. Nothing checks that the identifier names a volume that workspace owns. Parent-directory segments in the identifier collapse the joined path to the worker's filesystem root, and the worker bind-mounts that path into the sandbox read-write unless the volume was explicitly marked read-only. A tenant with a workspace token can therefore read and write the worker's files, including other tenants' volumes stored on that machine. Confirmed against gateway 0.1.769 and worker 0.1.745. Fixed in gateway 0.1.776 and worker 0.1.756: volume identifiers and mount paths are validated before a mount is built, including for stubs saved before the check existed, and the gateway rejects a volume that does not exist or is not owned by the workspace.
Title Beta9 host filesystem exposure via volume path traversal
Weaknesses CWE-22
CWE-668
References
Metrics cvssV3_1

{'score': 9.9, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H'}

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

  • CWE-668

    Exposure of Resource to Wrong Sphere

Sources

Status
PUBLISHED
Assigner
JFROG
Published
Updated
Nov 2, 2026, 7:45 PM
Reserved
Nov 1, 2026, 12:46 PM
Status
Deferred
Published
Nov 1, 2026, 1:18 PM
Modified
Nov 2, 2026, 8:17 PM