| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 1.64- |
Summary
A vulnerability was found in OpenClaw up to 2026.3.21. It has been classified as critical. The impacted element is an unknown function. Performing a manipulation results in incorrect user management. This vulnerability is identified as CVE-2026-35638. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, was found in OpenClaw up to 2026.3.21. This affects an unknown code block. The manipulation with an unknown input leads to a incorrect user management vulnerability. CWE is classifying the issue as CWE-286. The product does not properly manage a user within its environment. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
OpenClaw before 2026.3.22 contains a privilege escalation vulnerability in the Control UI that allows unauthenticated sessions to retain self-declared privileged scopes without device identity verification. Attackers can exploit the device-less allow path in the trusted-proxy mechanism to maintain elevated permissions by declaring arbitrary scopes, bypassing device identity requirements.
The weakness was released by KeenSecurityLab as GHSA-48vw-m3qc-wr99. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-35638 since 04/04/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 2026.3.22 eliminates this vulnerability. Applying the patch 630f1479c44f78484dfa21bb407cbe6f171dac87 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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
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: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.8
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: Incorrect user managementCWE: CWE-286
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.22
Patch: 630f1479c44f78484dfa21bb407cbe6f171dac87
Timeline
04/04/2026 CVE reserved04/10/2026 Advisory disclosed
04/10/2026 VulDB entry created
04/10/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-48vw-m3qc-wr99
Researcher: KeenSecurityLab
Status: Confirmed
CVE: CVE-2026-35638 (🔒)
GCVE (CVE): GCVE-0-2026-35638
GCVE (VulDB): GCVE-100-356781
Entry
Created: 04/10/2026 06:57Changes: 04/10/2026 06:57 (78)
Complete: 🔍
Cache ID: 216:5DA: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.