# CVE-2026-120306: Beta9 build sandbox escape via chroot-only isolation


- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-xvhg-75x6-gj86

## What is CVE-2026-120306?

CVE-2026-120306 is a critical vulnerability in beam-cloud Beta9 worker, published on 1 Nov 2026. 

### Official 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.

Weakness: CWE-653 (Improper Isolation or Compartmentalization), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-120306?


## How do I fix CVE-2026-120306?

No fix has been published for CVE-2026-120306 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120306 being exploited?

There is no known exploitation of CVE-2026-120306 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120306 and fix it if it is affected.

What it is: CVE-2026-120306 is a critical vulnerability in beam-cloud Beta9 worker, published on 1 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120306 in the wild and no public exploit code.

Affected product: beam-cloud Beta9 worker. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120306/ (Markdown: https://insights.sbomify.com/CVE-2026-120306/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120306
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120306
- OSV: https://osv.dev/vulnerability/CVE-2026-120306

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120306/
Summaries are generated and may contain mistakes; the official description above is the record.
