CVE-2026-22172
Authorization Bypass in OpenClaw WebSocket Enables Admin Access
Publication date: 2026-03-20
Last updated on: 2026-03-24
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.3.12 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-22172 is a critical authorization bypass vulnerability in OpenClaw versions prior to 2026.3.12 affecting the WebSocket connection path.
The flaw allows shared-token or password-authenticated WebSocket connections to self-declare elevated scopes without proper server-side binding.
Attackers can exploit this logic flaw to present unauthorized scopes such as operator.admin, enabling them to perform admin-only gateway operations without proper authorization.
How can this vulnerability impact me? :
This vulnerability allows attackers to escalate their privileges by self-declaring elevated scopes, such as operator.admin, on the OpenClaw gateway.
As a result, unauthorized users can perform administrative operations on the gateway, potentially compromising the confidentiality, integrity, and availability of the system.
Because the attack requires only low privileges and no user interaction, it can be exploited remotely over the network, making it highly dangerous.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate the CVE-2026-22172 vulnerability, you should upgrade OpenClaw to version 2026.3.12 or later, where the issue has been fixed.
The fix involves clearing unbound scopes for non-Control-UI shared-auth connections and adding regression tests to prevent this authorization bypass.