Which versions of OpenClaw are affected by CVE-2026-41352?

OpenClaw versions before 2026.3.31 contain a critical vulnerability enabling unauthorized remote code execution for attackers with device-pairing access, risking complete system compromise.. A patch is available.

How to fix or mitigate CVE-2026-41352?

Within 24 hours, identify all systems running OpenClaw prior to version 2026.3.31 and obtain the patched release (version 2026.3.31 or later). Within 7 days, deploy the patch across all instances using a staged rollout starting with production and mission-critical systems. Within 30 days, complete full deployment, verify patch application across all infrastructure, and conduct an access control review to restrict device-pairing credential issuance to authorized personnel only.

OpenClaw CVE-2026-41352

Q: What is the CVSS score of CVE-2026-41352?

CVE-2026-41352 has a CVSS 4.0 base score of 7.7 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.4%.

EUVD-2026-25336 HIGH

Missing Authorization (CWE-862)

2026-04-23 VulnCheck

GHSA-7vq9-42cc-33j4

Authentication Bypass RCE Openclaw

7.7

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

7.7 HIGH

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

7.5 HIGH

Network-reachable but requires held device-pairing credentials (PR:L) and the pairing/setup prerequisite raises attack complexity (AC:H); successful node command yields full host C/I/A impact.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Source Code Evidence Fetched

Jul 24, 2026 - 03:22 vuln.today

Analysis Generated

Jul 24, 2026 - 03:22 vuln.today

CVSS changed

Apr 23, 2026 - 22:28 NVD

8.8 (HIGH) 7.7 (HIGH)

EUVD ID Assigned

Apr 23, 2026 - 22:15 euvd

EUVD-2026-25336

Patch released

Apr 23, 2026 - 22:15 nvd

Patch available

CVE Published

Apr 23, 2026 - 21:58 nvd

HIGH 7.7

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1 npm packages depend on openclaw (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.3.31.

DescriptionCVE.org

OpenClaw before 2026.3.31 contains a remote code execution vulnerability where a device-paired node can bypass the node scope gate authentication mechanism. Attackers with device pairing credentials can execute arbitrary node commands on the host system without proper node pairing validation.

AnalysisAI

Authentication-bypass leading to remote code execution in OpenClaw before 2026.3.31 allows a node that is only device-paired to skip the node scope gate and invoke privileged node commands (including system.run) on the host. An attacker holding device-pairing credentials - but without the stricter node-pairing approval - can execute arbitrary commands with total impact to host confidentiality, integrity, and availability. No public exploit is identified at time of analysis; EPSS is low (0.37%, 59th percentile) and CISA SSVC records no known exploitation.

Technical ContextAI

OpenClaw is a Node.js/npm gateway (package 'openclaw') that brokers commands between paired client nodes and a host system over an RPC/WebSocket gateway (src/gateway/server). Access to node commands is intended to be governed by two distinct trust layers: a lightweight 'device pairing' and a stronger 'node pairing' scope gate that must approve the specific command allowlist (e.g. canvas.snapshot, system.run) with operator scopes. The root cause is CWE-862 (Missing Authorization): the server exposed node commands to a merely device-paired node without enforcing that node pairing existed, so the scope gate was effectively bypassed. The fix commit (3886b65) adds test coverage proving that a device-paired-only node must have all declared commands blocked ('node command not allowed') until node pairing is explicitly approved via requestNodePairing/approveNodePairing with operator.admin/operator.write scopes.

RemediationAI

Vendor-released patch: upgrade the openclaw npm package to 2026.3.31 or later, which is the first stable tag containing fix commit 3886b65ef21d02808c1a106fa1f9f69e22f71c32 and restores enforcement that node commands stay blocked until node pairing is explicitly approved. See the advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-xj9w-5r6q-x6v4 and the patch at https://github.com/openclaw/openclaw/commit/3886b65ef21d02808c1a106fa1f9f69e22f71c32. If you cannot upgrade immediately, revoke or tightly restrict device-pairing credentials so only fully trusted devices can reach the gateway, and network-isolate the gateway RPC/WebSocket endpoint so it is unreachable from untrusted networks; the trade-off is that legitimate remote nodes may lose connectivity until re-paired. Do not grant node command allowlists - especially system.run - to any node that has not completed the stronger node-pairing approval flow.