CVE-2026-43574
Improper Authorization in OpenClaw Before 2026.4.12
Publication date: 2026-05-05
Last updated on: 2026-05-05
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.4.12 (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
What immediate steps should I take to mitigate this vulnerability?
To mitigate the vulnerability in OpenClaw before version 2026.4.12, you should upgrade your OpenClaw installation to version 2026.4.12 or later, such as 2026.4.14, where the issue has been patched.
This update prevents empty approver lists from being interpreted as explicit approval authorization, thereby blocking attackers from resolving pending approvals without proper authorization.
Can you explain this vulnerability to me?
This vulnerability exists in OpenClaw versions before 2026.4.12 and involves an improper authorization issue in helper-backed channels.
Specifically, when the list of resolved approvers is empty, the system incorrectly interprets this as explicit approval authorization.
As a result, attackers who know an approval ID can exploit this logic flaw to resolve pending approvals without having proper authorization.
How can this vulnerability impact me? :
This vulnerability can allow unauthorized users to bypass normal approval processes by exploiting the improper authorization logic.
Attackers with knowledge of an approval ID can resolve pending approvals without permission, potentially leading to unauthorized actions or changes within the system.
This can undermine the integrity of approval workflows and may result in security breaches or misuse of privileges.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.