# CVE-2026-100573: OpenClaw before 2026.8.1 Sandbox Policy Bypass via MCP Loopback

> Attackers can bypass sandbox restrictions in OpenClaw to invoke denied tools, accessing restricted data or performing unauthorized actions.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-5m4g-88rg-69pj, GHSA-v9f5-4mfv-5533, MINI-9h8j-9v4w-qrh7

## What is CVE-2026-100573?

CVE-2026-100573 is a medium-severity vulnerability in OpenClaw, published on 26 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenClaw versions before 2026.8.1 contain a sandbox policy bypass vulnerability in the MCP loopback component that allows sandboxed coding-agent sessions to invoke tools explicitly denied by sandbox.tools.deny policy. Attackers can list and invoke denied tools to access data or perform actions the operator intended to exclude from the sandbox.

Weakness: CWE-862 (Missing Authorization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-100573 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100573 is a medium-severity vulnerability in OpenClaw, published on 26 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100573 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-100573/ (Markdown: https://insights.sbomify.com/CVE-2026-100573/index.md)
```

## Sources

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

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