CVE-2026-35643: OpenClaw: Arbitrary code execution via unvalidated WebView JavascriptInterface
In the OpenClaw Android app before 2026.3.22, any page loaded in the Canvas WebView could call the JavascriptInterface bridge and inject instructions into the app. A page from an untrusted origin could drive the agent without the user's intent. Upgrade openclaw to 2026.3.22 or later.
Published Mar 26, 2026 · Updated Apr 10, 2026 · Analysis Oct 31, 2026
What an attacker can do
The Android app shows Canvas pages in a WebView and exposes a JavascriptInterface, CanvasA2UIActionBridge, so page scripts can send actions to the app. Before the fix, CanvasScreen.kt did not check which page was calling. JavaScript from any origin the WebView loaded could post messages through the bridge.
Those messages are treated as instructions for the app, so this is injection into the agent's control channel (CWE-77, with CWE-940 for the unverified source). An attacker needs the WebView to load a page they control, for example through a link or content the agent shows. The CVSS vector marks user interaction as required (UI:R). With that, the attacker can issue actions with the app's authority, which the vector scores as high for confidentiality, integrity and availability.
Teams that run OpenClaw on Android alongside tools and accounts should treat a malicious Canvas page as a path to those tools.
Who is affected
Affected: the openclaw package before 2026.3.22, specifically the Android app built from apps/android. The desktop and server parts are not described as affected. Check the package and the installed Android app version:
npm ls openclawIn the Android settings, open the app info page and compare the app version with 2026.3.22.
openclaw
- Ecosystem
- npm
- Affected
- < 2026.3.22
- Fixed in
- 2026.3.22
- Check
npm ls openclaw
How to fix it
Update to openclaw 2026.3.22 or later, and install the matching Android app build. The version remains fixed in 2026.3.23 and 2026.3.23-2.
npm install -g openclaw@latestThe fix is commit 8b02ef133275be96d8aac2283100016c8a7f32e5. CanvasScreen.kt now tracks the current page URL, and the bridge returns early if the page is untrusted. CanvasActionTrust.kt trusts only the bundled scaffold asset and A2UI pages whose scheme, host, port and path match the configured canvas host. Other file: URLs and other origins are rejected. The advisory names no workaround.
How to tell if you were hit
Review which URLs the Android Canvas WebView loaded and whether any came from an origin other than your configured canvas host. Look for agent actions or tool calls that the user did not ask for around the time a Canvas page was shown. Check the app version on each device; anything below 2026.3.22 is vulnerable. The advisory publishes no log signatures.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
Android Canvas WebView pages from untrusted origins could invoke the JavascriptInterface bridge and inject instructions into the app.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected: < 2026.3.22
- Fixed: >= 2026.3.22
- Latest released tag checked:
v2026.3.23-2(630f1479c44f78484dfa21bb407cbe6f171dac87) - Latest published npm version checked:
2026.3.23-2
Fix Commit(s)
8b02ef133275be96d8aac2283100016c8a7f32e5
Release Status
The fix shipped in v2026.3.22 and remains present in v2026.3.23 and v2026.3.23-2.
Code-Level Confirmation
- apps/android/app/src/main/java/ai/openclaw/app/ui/CanvasScreen.kt now snapshots page origin and rejects untrusted bridge calls.
- apps/android/app/src/main/java/ai/openclaw/app/node/CanvasActionTrust.kt centralizes trusted origin and path validation for the bridge.
OpenClaw thanks @cyjhhh for reporting.
Credited to cyjhhh.
Questions
- Does CVE-2026-35643 affect the OpenClaw CLI on a server?
The advisory describes the Android Canvas WebView and its JavascriptInterface. It does not describe the server or CLI as exposed, though all openclaw versions before 2026.3.22 are listed as vulnerable.
- Does it need user interaction?
Yes. The CVSS vectors mark user interaction as required: the Canvas WebView has to load the attacker's page.
- What origins does the fixed app trust?
The bundled CanvasScaffold/scaffold.html asset and A2UI pages on the configured canvas host that match its scheme, host, port and path prefix. Anything else is dropped.
- Is it exploited in the wild?
No source says so, and the entry is not in CISA's KEV catalog. The EPSS score is 0.0036.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-62197
OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs
medium8.5Oct 21, 2026CVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026
