CVE-2026-45224: openclaw Crabbox path traversal in Islo provider workspace resolution

CVE-2026-45224 · Severity: high · CVSS 7.1 · Published 2026-05-11

Crabbox, a tool for managing sandboxed development environments, contains a security flaw in how it handles workspace paths for its Islo provider. An attacker can include a malicious configuration file in a repository that, when opened by a user, causes Crabbox to delete or overwrite critical system files within the sandbox environment. This could lead to data loss or the corruption of the isolated environment used for development tasks.

Technologies: github.com/openclaw/crabbox (Go), Openclaw Crabbox. Vendors: Go, Openclaw.

Quick answers

Is CVE-2026-45224 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-45224 being exploited in the wild.
How severe is CVE-2026-45224?
High severity, with a CVSS score of 7.1, published 11 May 2026.
Which products and versions are affected?
github.com/openclaw/crabbox (Go) < 0.9.0, SEMVER:introduced=0,fixed=0.9.0; Openclaw Crabbox < 0.9.0.
Is there a fix for CVE-2026-45224?
Yes. github.com/openclaw/crabbox (Go): upgrade to 0.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-45224 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2026-45224?
Check whether you run github.com/openclaw/crabbox (Go) or Openclaw Crabbox at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/openclaw/crabbox (Go): upgrade to 0.9.0 or later
    go get github.com/openclaw/crabbox@v0.9.0

Technical details

A path traversal vulnerability exists in Crabbox's Islo provider due to insufficient validation of the 'islo.workdir' parameter in configuration files (.crabbox.yaml or crabbox.yaml). The 'isloWorkspacePath()' function fails to properly sanitize absolute paths or relative paths containing traversal sequences (e.g., '../etc'), allowing them to resolve outside the intended '/workspace' directory. When 'sync.delete' is enabled, the workspace preparation logic executes 'rm -rf' and 'mkdir -p' on these resolved paths. An attacker can exploit this by tricking a user into running Crabbox against a malicious repository, leading to arbitrary file deletion or overwrites within the provider-side filesystem. This issue was addressed in version 0.9.0 by enforcing that all workdir paths are relative and contained strictly under the '/workspace' root.

Affected products

  • openclaw Crabbox < 0.9.0

Identifiers

  • CVE-2026-45224
  • GHSA-3cjv-h753-qf7h
  • GO-2026-5079

Timeline

  • 2026-05-09: patched: Fix merged in pull request #65
  • 2026-05-11: disclosed: CVE-2026-45224 published
  • 2026-05-11: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.