# CVE-2026-45224: Crabbox < 0.9.0 Path Traversal via Islo Provider Workspace Resolution


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 11 May 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-3cjv-h753-qf7h, GO-2026-5079

## What is CVE-2026-45224?

CVE-2026-45224 is a medium-severity vulnerability in openclaw crabbox, published on 11 May 2026. 

### Official description

Crabbox before 0.9.0 contains a path traversal vulnerability in the Islo provider's workspace path resolution that allows attackers to supply absolute or relative paths that resolve outside the intended /workspace directory. Attackers can craft a malicious .crabbox.yaml or crabbox.yaml file with traversal sequences to cause arbitrary file deletion and overwrite when sync.delete is enabled, as the workspace preparation logic executes rm -rf and mkdir -p operations on the resolved path without proper validation.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

3 open source packages ship an affected version, including github.com/openclaw/crabbox.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openclaw/crabbox` | Go | All versions | 0.9.0 |
| `github.com/openclaw/crabbox` | Go | All versions | 0.9.0 |
| `github.com/openclaw/crabbox` | Go | All versions | 0.9.0 |

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

Upgrade github.com/openclaw/crabbox to 0.9.0 or later.

## Is CVE-2026-45224 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45224 is a medium-severity vulnerability in openclaw crabbox, published on 11 May 2026. 
Exploitation: There is no known exploitation of CVE-2026-45224 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/openclaw/crabbox (Go): affected all versions; fixed in 0.9.0
- github.com/openclaw/crabbox (Go): affected all versions; fixed in 0.9.0
- github.com/openclaw/crabbox (Go): affected all versions; fixed in 0.9.0

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

## Sources

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

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