CVE-2026-120308 beam-cloud CVE debrief

Who should care

Defenders managing Beta9 deployments, especially those with multi-tenant environments, should assess exposure and apply patches to prevent unauthorized access. They should also review workspace configurations for proper volume access controls and verify the integrity of their deployments. Additionally, security teams and platform operators should be aware of the potential risks and take necessary precautions to protect their environments.

Why it matters

CVE-2026-120308 allows untrusted tenants to read and write worker files in Beta9, compromising tenant isolation and potentially leading to data breaches and lateral movement.

• Tenant isolation compromise, allowing read and write access to worker files
• Potential data breaches due to unauthorized access to sensitive files
• Increased risk of lateral movement within the environment
• Need for immediate patching and verification of workspace configurations

Technical summary

The Beta9 gateway and worker components have a vulnerability where a tenant can attach a volume and access files outside their workspace due to improper validation of volume identifiers. This allows a tenant with a workspace token to read and write the worker's files, including other tenants' volumes stored on that machine, compromising tenant isolation. Confirmed against gateway 0.1.769 and worker 0.1.745. Fixed in gateway 0.1.776 and worker 0.1.756: volume identifiers and mount paths are validated before a mount is built, including for stubs saved before the check existed, and the gateway rejects a volume that does not exist or is not owned by the workspace. This issue can lead to data breaches and lateral

Defensive priority

Defenders should prioritize verifying exposure of Beta9 deployments to untrusted tenants, reviewing workspace configurations, and applying the patch to gateway and worker components.

Recommended defensive actions

• Verify Beta9 deployments for exposure to untrusted tenants
• Review workspace configurations for proper volume access controls
• Apply patches to gateway and worker components to prevent unauthorized access
• Confirm whether affected Beta9 deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

Confirmed against gateway 0.1.769 and worker 0.1.745. Fixed in gateway 0.1.776 and worker 0.1.756: volume identifiers and mount paths are validated before a mount is built, including for stubs saved before the check existed, and the gateway rejects a volume that does not exist or is not owned by the workspace.

Sources and 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.