OpenClaw, an npm package, has a flaw before version 2026.7.1 that allows any caller with the write scope to use the node.invoke method to control a browser‑capable node without first being verified as an administrator. This bypass of the administrator scope check lets an attacker inspect page content, navigate tabs, or interact with browser‑visible applications, potentially exposing sensitive data or facilitating further attacks. The weakness is an example of improper authorization, listed as CWE-863.

The vulnerability affects all OpenClaw deployments that use the node.invoke API and are running any version older than 2026.7.1. The patch is available in the 2026.7.1 release. In Gateway configurations that honor caller identity and offer tighter operator scopes, the flaw is exploitable only when the caller holds write scope and the node is browser‑capable. Shared‑secret token and password callers are considered fully trusted and are not impacted. Identified product: OpenClaw npm package; version critical: >= 2026.7.1 is required for mitigation.

The CVSS score of 8.7 reflects a high‑severity vulnerability. No EPSS score is published, but the lack of a KEV listing does not preclude exploitation. The attack requires an attacker to have legitimate write‑scope access to a browser‑capable node and to invoke node.invoke. Because that access is granted only to operators within the OpenClaw security model, the threat is largely limited to compromised users or applications; nevertheless, once leveraged, the attacker can bypass the administrator requirement and perform unauthorised browser interactions. The vulnerability is directly exploitable through the node.invoke API and therefore can be triggered remotely by any entity that can send API requests to the OpenClaw Gateway.