Skip to main content
VulnerabilityPublished

CVE-2026-120307: beam-cloud Beta9 worker · Path Traversal

Affects beam-cloud Beta9 workerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.9 Critical : upgrade to 0.1.756 as a priority.

Data as of 1 Nov 2026, 13:13 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (JFROG)CVSS 3.19.9
Patch
Available – fixed in 0.1.756
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Upgrade Beta9 worker and github.com/beam-cloud/beta9 to 0.1.756.

Affected software

ProductAffectedFixed in
Beta9 workergithub.com/beam-cloud/beta9Affected
  • <0.1.756
Fixed in
  • 0.1.756
GitHubgithub.com/beam-cloud/beta9pkg:github/github.com/beam-cloud/beta9Other threatsAffected
  • <0.1.756
Fixed in
  • 0.1.756

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade the beam-cloud Beta9 worker to version 0.1.756 or later, where the vulnerability is fixed by confining file operations within container roots or mount sources using os.OpenRoot. No other mitigations are recommended as the fix fully addresses the path traversal issue.

Description

CVE-2026-120307 is a critical path traversal vulnerability in the beam-cloud Beta9 worker prior to version 0.1.756. It allows a tenant with a workspace token and running sandbox to perform file operations on the hosting worker's filesystem as root, including accessing files of other tenants. The flaw arises from improper path resolution that enables escaping the container root and accessing arbitrary paths on the worker. This includes reading sensitive files such as the Kubernetes service account token, which in default configurations has cluster-admin privileges. The issue is fixed in version 0.1.756 by restricting file operations to stay within container roots or mount sources.

References

Community reviews

Loading reviews…