| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OpenClaw up to 2026.4.19. It has been rated as problematic. This affects an unknown function. Performing a manipulation results in authorization. This vulnerability was named CVE-2026-45002. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability was found in OpenClaw up to 2026.4.19. It has been classified as problematic. This affects an unknown function. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as 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. This is going to have an impact on integrity. The summary by CVE is:
OpenClaw before 2026.4.20 contains a hook session-key bypass vulnerability that allows attackers to circumvent the hooks.allowRequestSessionKey opt-in restriction. Attackers can render externally influenced session keys through templated hook mappings to bypass webhook routing isolation controls.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-45002 since 05/08/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 2026.4.20 eliminates this vulnerability. Applying the patch 5275d008ed33203dba3f98e969ad683a65c416c3 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.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-29147). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 2026.4.0
- 2026.4.1
- 2026.4.2
- 2026.4.3
- 2026.4.4
- 2026.4.5
- 2026.4.6
- 2026.4.7
- 2026.4.8
- 2026.4.9
- 2026.4.10
- 2026.4.11
- 2026.4.12
- 2026.4.13
- 2026.4.14
- 2026.4.15
- 2026.4.16
- 2026.4.17
- 2026.4.18
- 2026.4.19
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.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
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: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: OpenClaw 2026.4.20
Patch: 5275d008ed33203dba3f98e969ad683a65c416c3
Timeline
05/08/2026 CVE reserved05/11/2026 Advisory disclosed
05/11/2026 VulDB entry created
05/12/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-2xcp-x87w-q377
Status: Confirmed
CVE: CVE-2026-45002 (🔒)
GCVE (CVE): GCVE-0-2026-45002
GCVE (VulDB): GCVE-100-362733
EUVD: 🔒
Entry
Created: 05/11/2026 20:39Updated: 05/12/2026 00:06
Changes: 05/11/2026 20:39 (77), 05/12/2026 00:06 (1)
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.