OpenClaw Command Authorization Bypass Vulnerability: Owner-Command Enforcement Skipped
Summary
GHSA-p73f-w79w-jqr5: OpenClaw: Native command authorization could skip owner-command enforcement. Affects openclaw versions < 2026.5.6. Fixed in 2026.5.6. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
OpenClaw is an open-source package designed for managing native commands in a secure manner. It allows authenticated Gateway operators to execute commands while maintaining a trusted-operator model. However, a recent vulnerability has been identified that could allow unauthorized users to bypass owner-command enforcement, potentially leading to unauthorized command execution.
Vulnerability Detail
The vulnerability arises from a flaw in the native command authorization process, where the configured owner-only command policy is not enforced. This means that a sender capable of triggering native command handling could authorize commands that should only be accessible to the owner. The practical impact of this vulnerability depends on the operator's configuration and whether lower-trust input can reach the vulnerable command path. If exploited, this could allow unauthorized execution of sensitive commands, posing a significant security risk.
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.5.6
This is the first release that contains the fix.
npm install openclaw@2026.5.6Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, limit native command surfaces to trusted senders until the patch is applied. Additionally, maintain narrow channel and tool allowlists, avoid sharing one Gateway between untrusted users, and disable the affected feature when it is not needed.
Conclusion
The OpenClaw vulnerability allows unauthorized users to bypass owner-command enforcement, posing a significant security risk. It is crucial to update to the patched version 2026.5.6 and implement workarounds to mitigate potential exploitation. Regular monitoring using tools like Vulert can help maintain security against such vulnerabilities.
See every vulnerability recorded for openclaw →
FAQ
The CVSS score of this vulnerability is 7.2, indicating a high severity level.
Versions of OpenClaw up to and including 2026.5.5 are affected by this vulnerability.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application's status using the Vulert playground at Vulert Scanner without any signup.
If you cannot update immediately, implement the suggested workarounds to limit exposure until you can apply the patch.
Yes, the trusted-operator model remains intact, but this vulnerability could allow unauthorized access to owner commands if not mitigated.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
