# CVE-2026-35570: OpenClaude has Sandbox Bypass via Early-Exit Logic Flaw that Allows Path Traversal

> Attackers can bypass sandbox restrictions to read arbitrary files via path traversal when auto-allow is enabled without deny rules.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A: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:** 20 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-m6rx-7pvw-2f73

## What is CVE-2026-35570?

CVE-2026-35570 is a high-severity path traversal vulnerability in Gitlawb openclaude, published on 20 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenClaude is an open-source coding-agent command line interface for cloud and local model providers. Versions prior to 0.5.1 have a logic flaw in `bashToolHasPermission()` inside `src/tools/BashTool/bashPermissions.ts`. When the sandbox auto-allow feature is active and no explicit deny rule is configured, the function returns an `allow` result immediately — before the path constraint filter (`checkPathConstraints`) is ever evaluated. This allows commands containing path traversal sequences (e.g., `../../../../../etc/passwd`) to bypass directory restrictions entirely. Version 0.5.1 contains a patch for the issue.

Weakness: CWE-284 (Improper Access Control), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

2 open source packages ship an affected version, including @gitlawb/openclaude. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@gitlawb/openclaude` | npm | All versions | 0.5.1 |
| `@gitlawb/openclaude` | npm | All versions | 0.5.1 |

Products: Gitlawb Openclaude.

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

Upgrade @gitlawb/openclaude to 0.5.1 or later.

## Is CVE-2026-35570 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35570 exists.

Public exploit code:

- https://github.com/Rickidevs/CVE-2026-35570 (github_poc): https://github.com/Rickidevs/CVE-2026-35570

## Other vulnerabilities in Gitlawb openclaude

- [CVE-2026-42074](https://insights.sbomify.com/CVE-2026-42074/): OpenClaude: Sandbox Bypass via Model-Controlled `dangerouslyDisableSandbox` Input (critical 9.3)
- [CVE-2026-42073](https://insights.sbomify.com/CVE-2026-42073/): OpenClaude's MCP OAuth Callback: State Check Bypass via error Param Leads to DoS (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-35570 is a high-severity path traversal vulnerability in Gitlawb openclaude, published on 20 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35570 exists.

Affected packages and fixed versions:
- @gitlawb/openclaude (npm): affected all versions; fixed in 0.5.1
- @gitlawb/openclaude (npm): affected all versions; fixed in 0.5.1

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

## Sources

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

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