| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in OpenClaw up to 2026.3.24. The affected element is an unknown function of the component Discord Handler. This manipulation causes authorization. This vulnerability appears as CVE-2026-41367. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability classified as problematic was found in OpenClaw up to 2026.3.24. Affected by this vulnerability is some unknown functionality of the component Discord Handler. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. As an impact it is known to affect integrity. The summary by CVE is:
OpenClaw versions 2026.2.14 through 2026.3.24 fail to consistently apply guild and channel policy gates to Discord button and component interactions. Attackers can trigger privileged component actions from blocked contexts by bypassing channel policy enforcement.
The weakness was presented by KeenSecurityLab and qclawer as GHSA-jp4j-q5fc-58gv. The advisory is shared at github.com. This vulnerability is known as CVE-2026-41367 since 04/20/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/29/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0930). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Open Source OpenClaw
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
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: 4.6VulDB Meta Temp Score: 4.6
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.0
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-863 / 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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/20/2026 CVE reserved04/28/2026 Advisory disclosed
04/28/2026 VulDB entry created
04/29/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-jp4j-q5fc-58gv
Researcher: KeenSecurityLab, qclawer
Status: Confirmed
CVE: CVE-2026-41367 (🔒)
GCVE (CVE): GCVE-0-2026-41367
GCVE (VulDB): GCVE-100-359893
CERT Bund: WID-SEC-2026-0930 - OpenClaw: Mehrere Schwachstellen
Entry
Created: 04/28/2026 06:37Updated: 04/29/2026 09:16
Changes: 04/28/2026 06:37 (75), 04/29/2026 09:16 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.