OpenClaw up to 2026.3.30 Restricted Message authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OpenClaw up to 2026.3.30. It has been rated as critical. This impacts an unknown function of the component Restricted Message Handler. The manipulation leads to authorization. This vulnerability is uniquely identified as CVE-2026-41406. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability was found in OpenClaw up to 2026.3.30. It has been rated as critical. This issue affects an unknown function of the component Restricted Message Handler. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
OpenClaw before 2026.3.31 contains a sender allowlist bypass vulnerability that allows remote attackers to access restricted messages. Attackers can exploit fetched quoted, root, and thread context messages to bypass sender allowlist restrictions and retrieve unauthorized content.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-41406 since 04/20/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 2026.3.31 eliminates this vulnerability. Applying the patch f45e5a6569aab1d58cc6de25b19f1dc4c8779b85 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 2026.3.0
- 2026.3.1
- 2026.3.2
- 2026.3.3
- 2026.3.4
- 2026.3.5
- 2026.3.6
- 2026.3.7
- 2026.3.8
- 2026.3.9
- 2026.3.10
- 2026.3.11
- 2026.3.12
- 2026.3.13
- 2026.3.14
- 2026.3.15
- 2026.3.16
- 2026.3.17
- 2026.3.18
- 2026.3.19
- 2026.3.20
- 2026.3.21
- 2026.3.22
- 2026.3.23
- 2026.3.24
- 2026.3.25
- 2026.3.26
- 2026.3.27
- 2026.3.28
- 2026.3.29
- 2026.3.30
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.4
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: OpenClaw 2026.3.31
Patch: f45e5a6569aab1d58cc6de25b19f1dc4c8779b85
Timeline
04/20/2026 CVE reserved04/28/2026 Advisory disclosed
04/28/2026 VulDB entry created
04/28/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-877v-w3f5-3pcq
Status: Confirmed
CVE: CVE-2026-41406 (🔒)
GCVE (CVE): GCVE-0-2026-41406
GCVE (VulDB): GCVE-100-360017
Entry
Created: 04/28/2026 21:54Changes: 04/28/2026 21:54 (78)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.