Crabbox Path Traversal Vulnerability (CVE-2026-45224)
Crabbox versions before 0.9.0 contain a path traversal vulnerability (CVE-2026-45224) in the Islo provider's workspace path resolution, allowing attackers to cause arbitrary file deletion and overwrite by crafting malicious .crabbox.yaml files with traversal sequences when sync.delete is enabled.
Crabbox, a software tool with unspecified functionality, is vulnerable to a path traversal flaw affecting versions prior to 0.9.0. The vulnerability lies within the Islo provider’s workspace path resolution logic. By supplying specially crafted .crabbox.yaml or crabbox.yaml files containing directory traversal sequences (e.g., ../), attackers can manipulate the application to resolve paths outside the intended /workspace directory. When the sync.delete option is enabled, this vulnerability allows for arbitrary file deletion and overwrite because the application uses rm -rf and mkdir -p on the attacker-controlled, resolved path without proper input sanitization. This can lead to significant data loss or system compromise.
Attack Chain
- Attacker crafts a malicious
.crabbox.yamlorcrabbox.yamlfile. - The malicious YAML file contains path traversal sequences (e.g.,
../) within the workspace path definition. - The attacker places the crafted YAML file in a location accessible to the Crabbox application.
- The Crabbox application processes the YAML file using the Islo provider.
- The Islo provider’s workspace path resolution logic resolves the attacker-supplied path, failing to properly sanitize directory traversal sequences.
- If
sync.deleteis enabled, the application executesrm -rfon the resolved (malicious) path, leading to arbitrary file deletion. - Subsequently, the application executes
mkdir -pon the resolved path, potentially overwriting existing files and directories. - The attacker achieves arbitrary file deletion and overwrite, potentially leading to data loss or system compromise.
Impact
Successful exploitation of CVE-2026-45224 allows attackers to delete or overwrite arbitrary files and directories on the system where Crabbox is running. The severity of the impact depends on the privileges of the Crabbox process and the location of the files that are targeted. A successful attack could lead to data loss, denial of service, or in some circumstances, even remote code execution if critical system files are overwritten.
Recommendation
- Upgrade Crabbox to version 0.9.0 or later to patch CVE-2026-45224.
- As a workaround, disable the
sync.deleteoption in Crabbox configurations to mitigate the file deletion aspect of the vulnerability. - Implement the Sigma rule “Detect Crabbox Path Traversal Attempt via Malicious YAML” to detect suspicious
.crabbox.yamlfiles containing path traversal sequences. - Monitor file system events for
rm -rfandmkdir -pcommands executed by the Crabbox process, especially when the target paths contain directory traversal sequences, using the Sigma rule “Detect Suspicious rm -rf or mkdir -p with Path Traversal”.
Detection coverage 2
Detect Crabbox Path Traversal Attempt via Malicious YAML
highDetects CVE-2026-45224 exploitation — Detects suspicious .crabbox.yaml or crabbox.yaml files containing path traversal sequences (../) indicating a potential path traversal attempt
Detect Suspicious rm -rf or mkdir -p with Path Traversal
mediumDetects suspicious rm -rf or mkdir -p commands with path traversal sequences, potentially related to CVE-2026-45224 exploitation
Detection queries are available on the platform. Get full rules →