OpenClaw up to 2026.5.25 Routes validate destination server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 4.35 |
Summary
A vulnerability classified as problematic has been found in OpenClaw up to 2026.5.25. Affected by this issue is the function validate of the component Routes. The manipulation of the argument destination leads to server-side request forgery.
This vulnerability is documented as CVE-2026-62227. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, has been found in OpenClaw up to 2026.5.25. This issue affects the function validate of the component Routes. The manipulation of the argument destination with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality. The summary by CVE is:
OpenClaw 2026.4.14 before 2026.5.26 contain a server-side request forgery vulnerability in browser snapshot routes that fail to validate post-navigation destinations. Attackers with lower-trust access can bypass OpenClaw policy checks to reach network destinations that should have been blocked.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-62227 since 07/13/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
Upgrading to version 2026.5.26 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-45115). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 2026.5.0
- 2026.5.1
- 2026.5.2
- 2026.5.3
- 2026.5.4
- 2026.5.5
- 2026.5.6
- 2026.5.7
- 2026.5.8
- 2026.5.9
- 2026.5.10
- 2026.5.11
- 2026.5.12
- 2026.5.13
- 2026.5.14
- 2026.5.15
- 2026.5.16
- 2026.5.17
- 2026.5.18
- 2026.5.19
- 2026.5.20
- 2026.5.21
- 2026.5.22
- 2026.5.23
- 2026.5.24
- 2026.5.25
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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: 🔒
Upgrade: OpenClaw 2026.5.26
Timeline
07/13/2026 CVE reserved07/17/2026 Advisory disclosed
07/17/2026 VulDB entry created
07/17/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-62227 (🔒)
GCVE (CVE): GCVE-0-2026-62227
GCVE (VulDB): GCVE-100-379721
EUVD: 🔒
Entry
Created: 07/17/2026 03:23Updated: 07/17/2026 06:58
Changes: 07/17/2026 03:23 (55), 07/17/2026 06:58 (1)
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.