Beta9 tenant isolation and volume path flaws
Three Beta9 flaws allow a tenant with a workspace token to escape intended worker isolation or expose worker files and other tenants' data.[2][3][4]
Fix. Upgrade the worker to 0.1.756 or later.[2][3][4][5][6][7]
Versions, remediation & sources
- Affected systems & conditions
- JFrog identifies worker versions before 0.1.756 for all three issues, and gateway versions before 0.1.776 for CVE-2026-120308. Exploitation requires a workspace token. CVE-2026-120306 is reached through an image build; CVE-2026-120307 also requires a running sandbox; CVE-2026-120308 involves deploying with an attached volume.[2][3][4]
- Remediation
- Upgrade the worker to 0.1.756 or later. For CVE-2026-120308, also upgrade the gateway to 0.1.776 or later. Confirm the versions actually deployed across the installation. The fixes were released on September 15, 2026; the November 1 CVE publication is not a new patch release.[2][3][4][5][6][7]
- Evidence at review time
- JFrog describes read-only proofs for CVE-2026-120306 and CVE-2026-120307, and reports confirmation of CVE-2026-120308 on specific older versions. The reviewed records do not report exploitation in the wild.[2][3][4]
- Related context
- CVE-2026-120306 concerns chroot-only image-build isolation. CVE-2026-120307 concerns sandbox file path traversal and symlink handling. CVE-2026-120308 concerns volume path traversal and ownership checks. Worker access may expose other tenants' files; the CNA describes privileged worker pods and Kubernetes service-account exposure in the first two cases.[2][3][4][7]