Authorization Mismatch in OpenClaw: Persistent Config Mutation Risk
Summary
GHSA-hfpr-jhpq-x4rm: OpenClaw: operator.write chat.send could reach admin-only config writes. Affects openclaw versions < 2026.3.7. Fixed in 2026.3.7. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
OpenClaw is an open-source gateway client designed for managing chat functionalities and configurations. It allows users to execute commands and manage settings through a chat interface. However, a vulnerability has been identified that permits unauthorized persistent configuration changes, posing a risk to the integrity of the system.
Vulnerability Detail
The vulnerability arises from an authorization mismatch in the OpenClaw package, specifically within the chat.send command. An authenticated client with operator.write permissions could exploit this flaw to perform unauthorized persistent configuration mutations using the /config set or /config unset commands. This issue is rooted in the fact that the command authorization checks were insufficient, allowing lower-privileged users to access admin-level configuration changes. The potential ramifications include unintended alterations to critical system settings, which could disrupt operations and compromise security.
How To Fix
Latest published version: 2026.10.6 as of 22 Oct 2026
npm install openclaw@2026.10.6Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2026.3.7
This is the first release that contains the fix.
npm install openclaw@2026.3.7Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, restrict access to the chat.send command for clients with operator.write permissions until the package is updated. This can help mitigate the risk of unauthorized configuration changes.
Conclusion
The OpenClaw vulnerability presents a significant risk due to an authorization mismatch that allows unauthorized configuration changes. Users are strongly advised to update to version 2026.3.7 to mitigate this risk and maintain the integrity of their systems.
See every vulnerability recorded for openclaw →
FAQ
The vulnerability allows authenticated clients with limited permissions to perform unauthorized persistent configuration changes through the chat.send command.
You can check your application's vulnerability status using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without signup.
The main consequence is unintended persistent configuration mutations, which could lead to operational disruptions and security issues.
If an immediate update is not possible, consider restricting access to the chat.send command for lower-privileged users as a temporary measure.
The CVSS score of this vulnerability is 4.3, indicating a moderate level of severity.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
