CVE-2026-120308
Received Received - Intake

Path Traversal in Beta9 Gateway and Worker

Publication date: 2026-11-01

Last updated on: 2026-11-01

Assigner: JFrog

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-01
Last Modified
2026-11-01
Generated
2026-11-01
AI Q&A
2026-11-01
EPSS Evaluated
N/A
NVD
CVE-2026-120308

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
beam-cloud Beta9 gateway 0
beam-cloud Beta9 worker 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
CWE-668 The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

A Beta9 tenant can attach a volume to a function, endpoint, or task queue deployment. The gateway constructs a host path by combining the shared volumes root, workspace name, and volume identifier. No validation checks if the volume belongs to the workspace. Attackers can use parent-directory segments in the identifier to escape to the worker's filesystem root, gaining read-write access to files, including other tenants' volumes. Fixed in gateway 0.1.776 and worker 0.1.756.

Detection Guidance

Check Beta9 gateway and worker versions. If using gateway 0.1.769 or earlier and worker 0.1.745 or earlier, the system is vulnerable. Inspect volume mount configurations for unauthorized path traversal attempts.

Impact Analysis

A tenant with a workspace token could read or modify sensitive files on the worker, including other tenants' data. This could lead to data theft, unauthorized modifications, or service disruption. The impact is severe due to the potential for cross-tenant access and filesystem compromise.

Compliance Impact

This vulnerability likely violates data protection requirements under GDPR and HIPAA, as it enables unauthorized access to sensitive data across tenants. Organizations using Beta9 may face compliance violations, legal penalties, and reputational damage due to potential data breaches.

Mitigation Strategies

Upgrade gateway to 0.1.776 and worker to 0.1.756 or later. Validate volume identifiers and mount paths to prevent path traversal. Ensure volume ownership checks are enforced before mounting.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-120308. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...