CVE-2026-100588 in OpenClaw
Summary
by MITRE • 09/26/2026
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.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 09/26/2026
The vulnerability identified in versions of the OpenClaw npm package prior to release 2026.7.1 represents a significant authorization bypass within the application’s browser control subsystem. Specifically, the flaw lies in the inconsistent enforcement of administrative scope requirements when accessing browser functionalities through different API entry points. While direct access via the browser.request method correctly mandates administrator-level privileges, the node.invoke method fails to apply this same restriction. This discrepancy creates an authentication and authorization gap that allows lower-privileged users to execute commands intended exclusively for administrators, thereby undermining the principle of least privilege central to secure system design.
In Gateway deployments where caller identity is honored and narrower operator scopes are configured, this technical flaw has tangible security implications. A user possessing only write-scoped access can leverage their connection to a browser-capable node to inspect web pages, navigate between tabs, or interact with applications visible within the browser environment. This capability exists without requiring the elevated administrative permissions that should be necessary for such actions. The practical impact of this vulnerability is contingent upon the specific configuration of the browser profile and whether users are currently signed into their accounts. If active sessions exist, an attacker could potentially access sensitive information or perform unauthorized interactions with web-based services, leading to data exposure or unintended state changes within those applications.
From a classification perspective, this issue aligns with CWE-269, which denotes Improper Privilege Management, as the system fails to enforce required administrative privileges for specific operations. Furthermore, it relates to CWE-862, Missing Authorization, because the application does not properly verify that the caller has the necessary permissions before allowing access to browser control features via the node.invoke method. In terms of offensive security frameworks such as MITRE ATT&CK, this vulnerability facilitates lateral movement and credential access techniques, particularly if an attacker can use the compromised browser session to harvest cookies or tokens from authenticated web applications.
The risk is mitigated by upgrading to OpenClaw version 2026.7.1 or later, where the code path for node.invoke has been corrected to enforce administrator scope requirements consistent with other privileged operations. It is important to note that this vulnerability does not affect callers using shared-secret tokens or passwords, as these authentication methods are considered fully trusted operators under OpenClaw’s security model and bypass standard role-based access controls entirely. Organizations relying on the affected versions should prioritize immediate patching to close this authorization gap and prevent potential exploitation by users with write-only permissions seeking elevated browser control capabilities.