Beta9 Worker: Sandbox path traversal (CVE-2026-120307)
The Beta9 worker contains a path traversal vulnerability in the sandbox file API that allows authenticated tenants to read, write, and delete arbitrary files on the host worker filesystem.
CVE search metadata
CVE search record: CVE-2026-120307. Severity: critical. CVSS: 9.9. KEV: no. Product: worker (< 0.1.756). Brief: Beta9 Worker: Sandbox path traversal (CVE-2026-120307). Brief link: https://feed.craftedsignal.io/briefs/2026-11-beta9-worker-traversal/
Triage facts
Revision 1- Applicability
- worker (< 0.1.756)
- Evidence
- Unknown
- Severity
- Critical
- Action
- Immediate escalation
- Sources
- 1 public source
- Freshness
- Revision 1Nov 1, 14:53 UTC
- Vulnerabilities
- 1 CVE
- Source quality
- A1Likely
Beta9 worker versions prior to 0.1.756 are vulnerable to a path traversal flaw in the sandbox file API due to improper sanitization in the getHostPathFromContainerPath function. Attackers with a valid workspace token and an active sandbox can perform unauthorized file operations on the host worker filesystem. This access can be used to read or modify data belonging to other tenants and, in cases where the worker pod is assigned cluster-admin permissions, can lead to full cluster compromise. The vulnerability is confirmed to allow reading the Kubernetes service account token.
Attack Chain
- Attacker gains access to a valid tenant workspace token.
- Attacker initiates or uses an active sandbox session.
- Attacker crafts a file path containing sequences that bypass the mount destination prefix check.
- The getHostPathFromContainerPath function resolves the malicious path to an absolute path on the host worker filesystem.
- The file API calls (Upload, download, stat, list, find-in-files, replace-in-files, or delete-file) interact with the resolved host path.
- The attacker reads or modifies sensitive host files, such as the Kubernetes service account token.
- If applicable, the attacker uses the stolen service account token to achieve cluster-admin access.
Impact
An attacker can achieve full read, write, and delete access to the host worker filesystem as root. This allows for the exfiltration of data from other tenants on the same worker and potential cluster-wide privilege escalation if the worker pod is configured with elevated Kubernetes permissions.
Recommendation
- Upgrade the Beta9 worker to version 0.1.756 or later immediately to implement os.OpenRoot for sandbox file operations.
- Audit Kubernetes RBAC configurations for worker pods to ensure the principle of least privilege is applied, specifically restricting cluster-admin access for worker pods.
- Review access logs for the sandbox file API for anomalous path requests involving multiple parent-directory segments.
Immediate actions
Upgrade Beta9 worker to 0.1.756
Threat Hunt
Identify requests to the sandbox file API containing parent-directory traversal patterns
Data: Application-level access logs for sandbox file API (e.g., path parameters)
Mitigations
Restrict Kubernetes service account permissions for worker pods
Cluster-wide compromise risk