Which versions of Openclaw are affected by CVE-2026-32057?

CVE-2026-32057 presents moderate security risk rated CVSS 6.0. Exploitation could compromise the security of affected deployments. Proof-of-concept code is publicly available.. A patch is available.

Is there a public PoC exploit available for CVE-2026-32057?

Yes, a public proof-of-concept exploit is available for CVE-2026-32057. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2026-32057?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Vendor patch is available.

Openclaw CVE-2026-32057

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

CVE-2026-32057 has a CVSS 4.0 base score of 6.0 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/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.1%.

EUVD-2026-13960 MEDIUM

Reliance on Untrusted Inputs in a Security Decision (CWE-807)

2026-03-21 VulnCheck

Authentication Bypass Openclaw

6.0

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

6.0 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

PoC Detected

Mar 25, 2026 - 15:16 vuln.today

Public exploit code

EUVD ID Assigned

Mar 21, 2026 - 01:00 euvd

EUVD-2026-13960

Analysis Generated

Mar 21, 2026 - 01:00 vuln.today

Patch released

Mar 21, 2026 - 01:00 nvd

Patch available

CVE Published

Mar 21, 2026 - 00:42 nvd

MEDIUM 6.0

DescriptionCVE.org

OpenClaw versions prior to 2026.2.25 contain an authentication bypass vulnerability in the trusted-proxy Control UI pairing mechanism that accepts client.id=control-ui without proper device identity verification. An authenticated node role websocket client can exploit this by using the control-ui client identifier to skip pairing requirements and gain unauthorized access to node event execution flows.

AnalysisAI

OpenClaw versions before 2026.2.25 allow authenticated attackers with node role permissions to bypass device pairing requirements in the Control UI by spoofing the control-ui client identifier, enabling unauthorized access to node event execution flows. Public exploit code exists for this authentication bypass vulnerability. The vulnerability requires prior authentication and has moderate integrity impact potential.

Technical ContextAI

The vulnerability exists in OpenClaw's trusted-proxy Control UI pairing mechanism, a component responsible for authenticating and authorizing websocket clients before granting access to node event execution capabilities. The root cause, classified under CWE-807 (Reliance on Untrusted Inputs in a Security Decision), stems from the system accepting the client.id parameter (specifically the hardcoded value 'control-ui') without verifying the actual device identity or legitimacy of the requesting entity. OpenClaw (cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) uses websocket-based communication for node orchestration and event handling; the pairing mechanism is intended to enforce a cryptographic or cryptographic-adjacent handshake between authorized control interfaces and worker nodes. By failing to validate that the connecting entity is actually a legitimate control-ui instance—rather than merely checking for the presence of that identifier—the system allows any authenticated websocket client with node role privileges to assume control-ui authority and access protected event execution flows.

RemediationAI

Upgrade OpenClaw to version 2026.2.25 or later to apply the security patch (commit ec45c317f5d0631a3d333b236da58c4749ede2a3). Organizations unable to patch immediately should implement the following mitigations: restrict websocket connections to the OpenClaw trusted-proxy to a whitelist of known control-ui endpoint IP addresses or hostnames, enforce mutual TLS (mTLS) authentication with certificate pinning for control-ui pairing handshakes, and implement detailed audit logging on all websocket client.id parameter values to detect attempted spoofing. Monitor for connections presenting client.id=control-ui from unexpected sources and implement network segmentation to isolate node websocket listeners from untrusted networks. See the vendor advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-vvgp-4c28-m3jm for official guidance.