Metrics
Affected Vendors & Products
No advisories yet.
Solution
Upgrade the Beta9 worker to 0.1.756 or later. That release drops chroot isolation: Buildah RUN steps use OCI isolation with private PID, IPC, and network namespaces, and tenant build arguments are applied inside the build container rather than in the Buildah process environment. The fix is commit a28bf12 (pull request 1897), released as worker-0.1.756 on 2026-09-15. Gateway 0.1.776 is the gateway tag cut from the same commit; the isolation change itself is in the worker image.
Workaround
No workaround given by the vendor.
Sun, 01 Nov 2026 13:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Beta9 turns each shell command in a tenant image definition into a Dockerfile RUN line and executes it with Buildah on the build worker. The worker image sets BUILDAH_ISOLATION=chroot, and no buildah invocation passes --isolation, so the step only changes its filesystem root. It keeps the worker pod's PID, network, IPC, and user namespaces, runs as uid 0, and holds CAP_DAC_OVERRIDE. PID 1 in that procfs is the worker entrypoint, so /proc/1/root is the worker container's filesystem and is writable. That filesystem contains the runc, buildah, and runsc binaries the worker uses to start tenant containers, the worker's Kubernetes service account token, and the host directories mounted into the pod. Worker pods are privileged. Clip v2 layered builds are the default, so a tenant with a workspace token reaches this by submitting one image build. The read-only proof confirmed the shared namespaces, CAP_DAC_OVERRIDE, and that the worker's runc binary is visible at /proc/1/root. Fixed in worker 0.1.756: Buildah RUN steps, including the WORKDIR mkdir, use OCI isolation with private PID, IPC, and network namespaces, and tenant ARG values are passed only into the build container. | |
| Title | Beta9 build sandbox escape via chroot-only isolation | |
| Weaknesses | CWE-269 CWE-653 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: JFROG
Published:
Updated: 2026-11-01T12:49:05.857Z
Reserved: 2026-11-01T12:32:40.057Z
Link: CVE-2026-120306
No data.
Status : Received
Published: 2026-11-01T13:18:01.300
Modified: 2026-11-01T13:18:01.300
Link: CVE-2026-120306
No data.
OpenCVE Enrichment
No data.