PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-120306 beam-cloud CVE debrief

A critical vulnerability was found in Beta9, a system used for building tenant image definitions. The vulnerability allows a tenant with a workspace token to execute arbitrary commands on the build worker, potentially leading to a compromise of the worker pod and containers. The issue arises from the way 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 is set to use chroot isolation, but it runs as uid 0 and holds CAP_DAC_OVERRIDE, allowing it to modify the filesystem. The vulnerability has been fixed in worker version 0.1.756, which uses OCI isolation with private PID, IPC, and network namespaces for Buildah RUN steps.

Vendor
beam-cloud
Product
Beta9 worker
CVSS
CRITICAL 9.9
CISA KEV
Not listed in stored evidence
Original CVE published
2026-11-01
Original CVE updated
2026-11-01
Advisory published
2026-11-01
Advisory updated
2026-11-01

Who should care

System administrators and security teams responsible for managing and securing Beta9 installations should assess their exposure and take immediate action to upgrade to a fixed version and restrict access to workspace tokens.

Why it matters

A critical vulnerability in Beta9 allows tenants to execute arbitrary commands on the build worker, potentially leading to worker pod and container compromise. Immediate action is required to upgrade to a fixed version and restrict access to workspace tokens.

  • Potential execution of arbitrary commands on the build worker
  • Possible compromise of worker pods and containers
  • Modification of worker filesystem and container configurations
  • Verification of worker integrity and container security

Technical summary

The vulnerability arises from the way Beta9 executes shell commands in tenant image definitions using Buildah on the build worker. The worker image uses chroot isolation but runs as uid 0 with CAP_DAC_OVERRIDE, allowing filesystem modifications. Tenant commands can modify the worker's filesystem, potentially leading to worker pod and container compromise. The issue allows a tenant with a workspace token to execute arbitrary commands on the build worker, potentially leading to a compromise of the worker pod and containers. The worker pods are privileged, and Clip v2 layered builds are the default, so a tenant can reach this by submitting one image build. The read-only proof confirmed the shared namespaces, CAP_D

Defensive priority

High

Recommended defensive actions

  • Immediately upgrade to worker version 0.1.756 or later
  • Restrict access to workspace tokens
  • Monitor worker pod and container logs for suspicious activity
  • Verify the integrity of the worker filesystem and container configurations
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability was confirmed through a read-only proof that verified the shared namespaces, CAP_DAC_OVERRIDE, and the visibility of the worker's runc binary at /proc/1/root. The fix was confirmed in worker version 0.1.756.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-120306 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-120306

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-120306 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-120306

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.