CVE-2026-35643
Openclaw ≤ 2026.3.22
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/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:XSummary
CVE-2026-35643 is a high-severity Improper Verification of Source of a Communication Channel (CWE-940) vulnerability in Openclaw Openclaw. Its CVSS base score is 8.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique ARP Cache Poisoning (T1557.002); ranked at the 30th 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-17 (Remote Access) and IA-3 (Device Identification and Authentication) — 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-35643 is an unvalidated WebView JavascriptInterface vulnerability in OpenClaw versions prior to 2026.3.22. The flaw enables attackers to inject arbitrary instructions by exploiting the canvas bridge, allowing untrusted web pages loaded in the Android application's WebView to execute malicious code within the application's context. This issue is classified under CWE-940 and carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), indicating high severity due to its potential for significant impact.
Attackers can exploit this vulnerability remotely over the network with low complexity and no required privileges, though it necessitates user interaction, such as loading a malicious or compromised web page in the affected WebView. Successful exploitation grants arbitrary code execution in the Android application context, potentially leading to high confidentiality, integrity, and availability impacts, including data theft, app compromise, or further system-level attacks depending on app permissions.
Mitigation is addressed in OpenClaw patches via GitHub commits 630f1479c44f78484dfa21bb407cbe6f171dac87 and 8b02ef133275be96d8aac2283100016c8a7f32e5, with full details in the project's security advisory at GHSA-cxmw-p77q-wchg. Security practitioners should update to OpenClaw 2026.3.22 or later and review VulnCheck's advisory at www.vulncheck.com/advisories/openclaw-arbitrary-code-execution-via-unvalidated-webview-javascriptinterface for additional analysis.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-21438
Vulnerability Data
OpenClaw before 2026.3.22 contains an unvalidated WebView JavascriptInterface vulnerability allowing attackers to inject arbitrary instructions. Untrusted pages can invoke the canvas bridge to execute malicious code within the Android application context.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.5.3V10.6.2V15.2.4
Mitigating Controls (NIST 800-53 r5) AI
IA-3 requires unique identification and authentication of devices before any communication channel is established, directly stopping acceptance of unverified origins.
AC-17 mandates documented restrictions and authentication requirements for remote access, blocking channels whose origins are not properly verified.
SC-23 protects session authenticity, ensuring the source of an established communication channel is verified and cannot be spoofed.
SC-7 enforces monitoring and control at external and key internal interfaces, preventing channels from unverified sources via boundary rules.
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.
Authentication of users/services/hardware directly enforces source verification for communication channels.
Verifying identity assertions prevents spoofed channel origins but does not cover all channel-establishment scenarios.
Network protections reduce unauthorized channel usage but do not specifically require origin verification at channel setup.
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 authentication mechanisms verify the identity and origin of communication channel initiators.
Network security controls enforce source verification and channel authentication for incoming communications.
Security of network services includes validating the origin of service requests and connections.
Network segregation limits exposure but does not directly verify source of individual channels.
Cryptography can support channel authentication but does not inherently verify source without proper implementation.
Application security requirements may specify origin checks but do not mandate them.