| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in OpenClaw up to 2026.4.28. This impacts an unknown function. The manipulation leads to authorization. This vulnerability is uniquely identified as CVE-2026-35673. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability was found in OpenClaw up to 2026.4.28 and classified as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
OpenClaw before 2026.4.29 contains an SSRF policy bypass vulnerability in browser debug and export routes that allows reuse of already-open blocked tabs. Attackers with access to these routes can bypass private-network SSRF policies by reusing blocked tabs to export or inspect content that should remain protected.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-35673 since 04/04/2026. The exploitation is known to be difficult. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 2026.4.29 eliminates this vulnerability.
The vulnerability is also documented in the databases at EUVD (EUVD-2026-33336) and CERT Bund (WID-SEC-2026-1738). 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.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
- 2026.4.20
- 2026.4.21
- 2026.4.22
- 2026.4.23
- 2026.4.24
- 2026.4.25
- 2026.4.26
- 2026.4.27
- 2026.4.28
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.7VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
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.29
Timeline
04/04/2026 CVE reserved05/29/2026 Advisory disclosed
05/29/2026 VulDB entry created
06/14/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-hcm3-8f6r-6xwg
Status: Confirmed
CVE: CVE-2026-35673 (🔒)
GCVE (CVE): GCVE-0-2026-35673
GCVE (VulDB): GCVE-100-367277
EUVD: 🔒
CERT Bund: WID-SEC-2026-1738 - OpenClaw: Mehrere Schwachstellen
Entry
Created: 05/29/2026 18:59Updated: 06/14/2026 05:57
Changes: 05/29/2026 18:59 (75), 05/30/2026 04:10 (1), 06/14/2026 05:57 (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.