OpenClaw Command Execution Vulnerability: Bypass of Approval Mechanism

openclaw Updated 04 Mar 2026

Summary

02/03/2026

Disclosed on

MODERATE

Severity

Yes i

Fix available

Moderate

Severity

6.4

CVSS Score

GHSA-6j27-pc5c-m8w8: OpenClaw's allow-always wrapper persistence could bypass future approvals and enable command execution. Affects openclaw versions < 2026.2.22. Fixed in 2026.2.22. 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 the execution of system commands in a controlled manner. It allows users to wrap commands with security features to prevent unauthorized execution. However, a flaw in its implementation has led to a vulnerability that can allow malicious commands to be executed without proper approval, compromising system security.

Vulnerability Detail

The vulnerability arises from the 'allow-always' wrapper persistence in OpenClaw versions up to and including 2026.2.21-2. When commands are approved with 'allow-always' in 'security=allowlist' mode, it can lead to the persistence of wrapper-level allowlist entries. This allows future commands to bypass approval checks, potentially leading to remote code execution (RCE). The issue stems from the fact that the persistence mechanism is based on wrapper-level resolution rather than the intent of the inner executable, broadening trust boundaries and exposing systems to unauthorized command execution.

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.22

This is the first release that contains the fix.

npm install openclaw@2026.2.22

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

Workaround

Until the upgrade is applied, users can mitigate the risk by running OpenClaw with a stricter execution policy. This can be achieved by setting the following parameters: 'ask=always' and 'security=deny'. This will prompt for approval on every command execution and deny any unapproved commands.

Conclusion

The OpenClaw vulnerability presents a significant risk by allowing command execution without proper authorization. Users are strongly advised to upgrade to the patched version 2026.2.22 or implement stricter execution policies to safeguard their systems. Utilizing tools like Vulert can also help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for openclaw →