Crabbox contains a path traversal vulnerability in the Islo provider's workspace path resolution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2026-45224: 0.14% estimated exploitation activity in the next 30 days; percentile 3.71 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

11 May 2026, 21:31 UTC

Last modified by the source

18 May 2026, 16:48 UTC

Source last checked

26 Oct 2026, 15:22 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3cjv-h753-qf7h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45224

Advisory: Crabbox contains a path traversal vulnerability in the Islo provider's workspace path resolution
IDs: CVE-2026-45224, GHSA-3cjv-h753-qf7h
Record: https://patchnext.com/advisories/cve-2026-45224 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/openclaw/crabbox 0.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/openclaw/crabbox: affected < 0.9.0; fixed in 0.9.0

## Suggested inspection (read-only)
- Go github.com/openclaw/crabbox: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/openclaw/crabbox.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3cjv-h753-qf7h (GitHub-reviewed advisory GHSA-3cjv-h753-qf7h lists affected ranges: Go github.com/openclaw/crabbox >=0 <0.9.0)

Commands are suggestions: review each one before running it.