CVE-2026-100588: OpenClaw before 2026.7.1 Authentication Bypass via node.invoke
OpenClaw (npm package 'openclaw') before 2026.7.1 does not enforce the administrator scope requirement on browser control when it is reached through the node.invoke method, although direct browser.request access requires administrator scope. In Gateway deployments that honor caller identity and narrower operator scopes, a write-scoped caller with access to a connected browser-capable node can inspect pages, navigate tabs, or interact with browser-visible applications without the configured admin requirement; practical impact depends on the browser profile and signed-in state. Shared-secret token and password callers are considered fully trusted operators under OpenClaw's security model and are not affected. The issue is fixed in 2026.7.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/openclawto a version that resolves this vulnerability.Fixed in 2026.7.1
Event History
Frequently Asked Questions
Which deployments are actually exposed to this issue?
Gateway deployments that honor caller identity and use narrower operator scopes are exposed when a write-scoped caller can access a connected browser-capable node. The practical impact depends on the browser profile and whether it is signed in to browser-visible applications.
What access does an attacker need?
An attacker needs a write-scoped caller identity and access to a connected node with browser capability. They can use node.invoke to reach browser control without the administrator scope required for direct browser.request access.
Are shared-secret token or password-based callers affected?
No. OpenClaw considers shared-secret token and password callers fully trusted operators, so they are not affected by this scope-enforcement bypass.
What can an unauthorized write-scoped caller do through the bypass?
They may inspect pages, navigate tabs, or interact with applications visible in the connected browser. Access to signed-in applications depends on the browser's existing profile and session state.
What version fixes the issue?
The issue is fixed in OpenClaw 2026.7.1. Versions before 2026.7.1 are affected under the applicable Gateway and caller-scope conditions.