# CVE-2026-102806: OpenClaw before 2026.9.5 Sandbox Isolation Bypass via Media Pipelines

> Attackers can bypass sandbox isolation to read files from other sessions via media pipelines, compromising data confidentiality.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-8f5c-296x-75hm, MINI-wfg5-55fh-px7p

## What is CVE-2026-102806?

CVE-2026-102806 is a medium-severity missing authorization vulnerability in OpenClaw, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenClaw before 2026.9.5 contains an incorrect authorization vulnerability in the Gateway's local media root allowlist that breaks filesystem isolation between sandboxed sessions. Sandboxed sessions or untrusted content can cause the Gateway to read files from sibling session sandboxes or shared workspace directories through media pipeline functions that fail to restrict reads to the active session.

Weakness: CWE-863 (Incorrect Authorization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-102806 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102806 is a medium-severity missing authorization vulnerability in OpenClaw, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102806 in the wild and no public exploit code.

Affected product: OpenClaw. 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-102806/ (Markdown: https://insights.sbomify.com/CVE-2026-102806/index.md)
```

## Sources

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

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