Unauthorized Sender Bypass in OpenClaw: Command Authorization Flaw

openclaw Updated 04 Mar 2026

Summary

02/03/2026
MODERATE
Yes i
Moderate
6.9

GHSA-8m9v-xpgf-g99m: OpenClaw has an unauthorized sender bypass in its stop triggers and /models command authorization. Affects openclaw versions < 2026.3.1. Fixed in 2026.3.1. 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 open-source package designed for natural language processing and command execution. It allows users to interact with applications using natural language commands. However, a critical vulnerability has been identified that permits unauthorized senders to bypass sender authorization checks, potentially leading to unauthorized command execution and data exposure.

Vulnerability Detail

The vulnerability arises from a lack of sender authorization checks in two specific command paths: stop-like natural-language abort triggers and the '/models' command output. This oversight allows unauthorized users to disrupt active sessions and access model and authentication metadata that should be restricted. The absence of proper authorization mechanisms poses a significant risk to the integrity and confidentiality of the application.

How To Fix

Minimum fixed version

2026.3.1

This is the first release that contains the fix.

npm install openclaw@2026.3.1

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

Workaround

Currently, there are no specific workarounds recommended for this vulnerability. The best course of action is to update to the patched version as soon as possible.

Conclusion

The unauthorized sender bypass vulnerability in OpenClaw poses significant risks by allowing unauthorized access to command execution and sensitive data. It is essential for users to update to the patched version 2026.3.1 to ensure the security of their applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The vulnerability allows unauthorized senders to bypass authorization checks for certain commands, leading to potential disruption and data exposure.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

The CVSS score of this vulnerability is 6.9, indicating a moderate severity level.

While there are no specific workarounds, it is crucial to prioritize updating to the patched version as soon as possible to mitigate risks.

You can find more information about OpenClaw and its functionalities on its official GitHub repository.

Related vulnerabilities

Recent vulnerabilities recorded for openclaw.

How To Fix

Minimum fixed version

2026.3.1

This is the first release that contains the fix.

npm install openclaw@2026.3.1

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.