CVE-2026-35649
Access Control Bypass in OpenClaw via Empty Allowlist Handling
Publication date: 2026-04-10
Last updated on: 2026-04-13
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.3.22 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-183 | The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are explicitly allowed by policy because the inputs are assumed to be safe, but the list is too permissive - that is, it allows an input that is unsafe, leading to resultant weaknesses. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in OpenClaw allows attackers to bypass intended deny-all revocations by exploiting improper handling of empty allowlists, effectively restoring previously revoked permissions. This improper authorization (CWE-285 and CWE-863) could lead to unauthorized access to sensitive data or resources.
Such unauthorized access could potentially impact compliance with standards and regulations like GDPR or HIPAA, which require strict access controls and protection of sensitive personal or health information. By silently undoing access denials, the vulnerability undermines the enforcement of access policies, increasing the risk of data exposure or misuse.
Therefore, organizations using affected versions of OpenClaw may face challenges in maintaining compliance with these regulations until the vulnerability is patched.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves verifying if your OpenClaw installation is running a version prior to 2026.3.22, as those versions improperly handle empty allowlists during settings reconciliation.
Since the vulnerability relates to authorization bypass caused by empty allowlists being treated as unset, you can check your system's allowlist configurations to identify any explicit empty allowlists that might be silently bypassing deny-all revocations.
There are no specific commands provided in the resources to detect exploitation attempts or the presence of this vulnerability on your network or system.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade OpenClaw to version 2026.3.22 or later, where the vulnerability has been fixed.
The fix ensures that explicit empty allowlists are treated as authoritative deny-all settings, preventing the bypass of intended access control denials.
If upgrading immediately is not possible, review and avoid using explicit empty allowlists in your settings reconciliation to prevent unintended permission restoration.
Can you explain this vulnerability to me?
This vulnerability exists in OpenClaw versions before 2026.3.22 and involves a flaw in the settings reconciliation process. Specifically, it allows attackers to bypass intended deny-all revocations by exploiting how empty allowlists are handled. The system treats explicit empty allowlists as if they were unset during reconciliation, which silently reverses intended access control denials and restores permissions that were previously revoked.
How can this vulnerability impact me? :
The impact of this vulnerability is that attackers can regain access to resources or permissions that were supposed to be denied or revoked. This means that security controls intended to restrict access can be bypassed, potentially allowing unauthorized access to sensitive data or system functions.