# CVE-2026-120308: Beta9 host filesystem exposure via volume path traversal


- **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-92w2-g272-fr77

## What is CVE-2026-120308?

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

### Official description

A Beta9 tenant can attach a volume when deploying a function, endpoint, or task queue. The gateway builds the host path by joining the shared volumes root, the workspace name, and the volume identifier from the stub configuration. Nothing checks that the identifier names a volume that workspace owns. Parent-directory segments in the identifier collapse the joined path to the worker's filesystem root, and the worker bind-mounts that path into the sandbox read-write unless the volume was explicitly marked read-only. A tenant with a workspace token can therefore read and write the worker's files, including other tenants' volumes stored on that machine. 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.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-120308 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: beam-cloud Beta9 gateway. 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-120308/ (Markdown: https://insights.sbomify.com/CVE-2026-120308/index.md)
```

## Sources

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

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