CVE-2026-32057
Openclaw ≤ 2026.2.25
Raw 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:XSummary
CVE-2026-32057 is a medium-severity Reliance on Untrusted Inputs in a Security Decision (CWE-807) vulnerability in Openclaw Openclaw. Its CVSS base score is 6.0 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-32057 is an authentication bypass vulnerability (CWE-807) in OpenClaw versions prior to 2026.2.25. The flaw exists in the trusted-proxy Control UI pairing mechanism, which accepts the client.id=control-ui parameter without performing proper device identity verification, published on 2026-03-21.
An authenticated node role WebSocket client can exploit this vulnerability over the network with low complexity and no user interaction. By using the control-ui client identifier, the attacker bypasses pairing requirements to gain unauthorized access to node event execution flows, resulting in low confidentiality impact, high integrity impact, and no availability impact. The CVSS v3.1 base score is 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N).
Advisories recommend upgrading to OpenClaw version 2026.2.25 or later, where the issue is addressed via the patch in GitHub commit ec45c317f5d0631a3d333b236da58c4749ede2a3. Additional details on the vulnerability and remediation are provided in the GitHub Security Advisory at GHSA-vvgp-4c28-m3jm and the Vulncheck advisory at https://www.vulncheck.com/advisories/openclaw-authentication-bypass-via-control-ui-client-id-parameter.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-13960
Vulnerability Data
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…
more
to skip pairing requirements and gain unauthorized access to node event execution flows.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Explicitly requires that every access decision be based on authoritative, protected decision data rather than caller-supplied inputs.
Input validation can reject malformed or attacker-controlled values before they reach a security decision point.
Access enforcement requires decisions to be made from trusted policy data rather than modifiable client-supplied inputs.
Information-flow enforcement applies rules to validated, internal attributes instead of untrusted external values.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Strong authentication mechanisms directly prevent security decisions from depending on modifiable, untrusted inputs.
Verification and protection of identity assertions stops reliance on attacker-controlled values for authorization decisions.
Proper management of identities/credentials reduces the chance that security decisions will be driven by untrusted inputs.
Policy-driven, least-privilege authorization reduces opportunities to bypass controls via tampered inputs.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards directly prohibit using untrusted inputs for security-critical decisions.
Security testing in development catches input-validation flaws before deployment.
Monitoring can detect exploitation but does not stop the underlying weakness.
Application security requirements explicitly call for validation of inputs used in security decisions.
Secure architecture principles mandate treating all external inputs as untrusted.
Access-control rules can be bypassed if they rely on untrusted inputs.