High-Risk Vulnerability in OpenClaw: Shell-Env Trusted Prefix Fallback Allows Attacker-Controlled Binary Execution

openclaw Updated 04 Mar 2026

Summary

03/03/2026

Disclosed on

HIGH

Severity

Yes i

Fix available

High

Severity

8.5

CVSS Score

GHSA-p4wh-cr8m-gm6c: OpenClaw: shell-env trusted-prefix fallback allowed attacker-controlled binary execution via $SHELL. Affects openclaw versions >= 2026.2.22, < 2026.2.23. Fixed in 2026.2.23. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or Browse

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats

SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml

Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile

Javascript package-lock.json · yarn.lock · pnpm-lock.yaml

PHP composer.lock

Python poetry.lock · requirements.txt · Pipfile.lock

Go go.mod

Rust Cargo.lock

Ruby Gemfile.lock

Dart pubspec.lock

C/C++ conan.lock

Elixir mix.lock

Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Background

OpenClaw is an npm package designed to facilitate various functionalities in JavaScript applications. It allows developers to manage shell environments effectively. However, a recent vulnerability has been identified that compromises the security of the package, particularly in scenarios where the runtime environment can be influenced by an attacker.

Vulnerability Detail

The vulnerability arises from the shell-env fallback mechanism that accepts executable paths for the $SHELL variable. In affected versions, the selection process allows either a shell listed in /etc/shells or any executable under hardcoded trusted prefixes. This can lead to the execution of attacker-controlled binaries if the trusted-prefix directory is writable and the runtime $SHELL can be influenced. The ramifications include unauthorized access and potential system compromise, making this a significant security risk.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.2.23

This is the first release that contains the fix.

npm install openclaw@2026.2.23

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, you can manually ensure that the $SHELL variable points to a secure shell listed in /etc/shells and avoid using writable trusted-prefix directories for shell executables.

Conclusion

The OpenClaw package has a critical vulnerability that allows for the execution of attacker-controlled binaries due to a flawed shell-env fallback mechanism. It is essential to update to the patched version 2026.2.23 to mitigate this risk. Additionally, users should consider using Vulert for ongoing monitoring of vulnerabilities in their dependencies.

See every vulnerability recorded for openclaw →