OpenClaw up to 2026.2.25 deviceFamily authentication spoofing
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OpenClaw up to 2026.2.25. It has been classified as critical. This impacts an unknown function. The manipulation of the argument deviceFamily leads to authentication spoofing. This vulnerability is referenced as CVE-2026-32014. The attack needs to be initiated within the local network. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, has been found in OpenClaw up to 2026.2.25. This issue affects an unknown code block. The manipulation of the argument deviceFamily with an unknown input leads to a authentication spoofing vulnerability. Using CWE to declare the problem leads to CWE-290. This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
OpenClaw versions prior to 2026.2.26 contain a metadata spoofing vulnerability where reconnect platform and deviceFamily fields are accepted from the client without being bound into the device-auth signature. An attacker with a paired node identity on the trusted network can spoof reconnect metadata to bypass platform-based node command policies and gain access to restricted commands.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-32014 since 03/10/2026. The exploitation is known to be easy. Access to the local network is required for this attack. Technical details are known, but no exploit is available.
Upgrading to version 2026.2.26 eliminates this vulnerability. Applying the patch 7d8aeaaf06e2e616545d2c2cec7fa27f36b59b6a 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.2.0
- 2026.2.1
- 2026.2.2
- 2026.2.3
- 2026.2.4
- 2026.2.5
- 2026.2.6
- 2026.2.7
- 2026.2.8
- 2026.2.9
- 2026.2.10
- 2026.2.11
- 2026.2.12
- 2026.2.13
- 2026.2.14
- 2026.2.15
- 2026.2.16
- 2026.2.17
- 2026.2.18
- 2026.2.19
- 2026.2.20
- 2026.2.21
- 2026.2.22
- 2026.2.23
- 2026.2.24
- 2026.2.25
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: 6.7VulDB Meta Temp Score: 6.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.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: Authentication spoofingCWE: CWE-290 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
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.2.26
Patch: 7d8aeaaf06e2e616545d2c2cec7fa27f36b59b6a
Timeline
03/10/2026 CVE reserved03/20/2026 Advisory disclosed
03/20/2026 VulDB entry created
03/25/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-r65x-2hqr-j5hf
Status: Confirmed
CVE: CVE-2026-32014 (🔒)
GCVE (CVE): GCVE-0-2026-32014
GCVE (VulDB): GCVE-100-351965
Entry
Created: 03/20/2026 08:29Updated: 03/25/2026 00:35
Changes: 03/20/2026 08:29 (79), 03/25/2026 00:35 (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.