Command Injection Vulnerability in OpenClaw Package

openclaw Updated 04 Mar 2026

Summary

03/03/2026
MODERATE
Yes i
Moderate
5.1

GHSA-fg3m-vhrr-8gj6: OpenClaw has Windows Lobster shell fallback command injection in constrained fallback path. Affects openclaw versions >= 2026.1.21, < 2026.2.19. Fixed in 2026.2.19. 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

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.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

OpenClaw is an npm package designed to facilitate the execution of commands and scripts in a cross-platform manner. It provides a wrapper around command execution, allowing developers to run shell commands seamlessly. However, a recent vulnerability has been identified that affects its Windows Lobster extension, which can lead to command injection under specific conditions.

Vulnerability Detail

The vulnerability arises from the Lobster extension's fallback mechanism on Windows, which retries certain spawn failures by invoking the command shell with 'shell: true'. This fallback allows tool-provided arguments to be interpreted by 'cmd.exe', potentially leading to command injection if an attacker can control these arguments. The issue is particularly concerning in environments where local operators can influence the command execution flow, making it a moderate risk with a CVSS score of 5.1.

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

This is the first release that contains the fix.

npm install openclaw@2026.2.19

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

Workaround

As a temporary workaround, users can avoid using the Lobster extension on Windows or ensure that command arguments are strictly controlled and sanitized to prevent injection attacks.

Conclusion

In summary, the OpenClaw package has a command injection vulnerability due to its fallback mechanism on Windows. Users are advised to update to the patched version to mitigate this risk. For those unable to update, strict controls on command arguments should be implemented as a temporary measure.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The vulnerability is a command injection risk that occurs when the Lobster extension falls back to using the Windows command shell, allowing potentially malicious arguments to be executed.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By simply uploading your package-lock.json file, you can check for vulnerabilities without needing to install any software.

If you cannot update, consider avoiding the use of the Lobster extension on Windows or implement strict controls on command arguments to mitigate the risk of injection.

The CVSS score of this vulnerability is 5.1, indicating a moderate level of risk.

Detailed information about the vulnerability can be found in the advisory published on GitHub, which outlines the affected versions and the steps to fix the issue.

Related vulnerabilities

Recent vulnerabilities recorded for openclaw.

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

This is the first release that contains the fix.

npm install openclaw@2026.2.19

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback