OpenClaw (npm package 'openclaw') before 2026.7.1 does not enforce the administrator scope requirement on browser control when it is reached through… (CVE-2026-100588)
OpenClaw (npm package 'openclaw') versions before 2026.7.1 have a security vulnerability where the administrator scope requirement is not enforced on browser control when accessed via the node.invoke method. This allows a write-scoped caller with access to a connected browser-capable node to perform actions such as inspecting pages, navigating tabs, or interacting with browser-visible applications without needing administrator privileges. The vulnerability is fixed in version 2026.7.1.
AI Analysis
Technical Summary
The OpenClaw npm package prior to version 2026.7.1 does not enforce the administrator scope requirement on browser control when accessed through the node.invoke method, despite direct browser.request access requiring administrator scope. In Gateway deployments that respect caller identity and narrower operator scopes, this flaw allows a write-scoped caller to interact with browser-capable nodes beyond their intended privileges. Shared-secret token and password callers, considered fully trusted, are not affected. The issue is resolved in version 2026.7.1.
Potential Impact
An attacker or user with write-scoped access to a connected browser-capable node can inspect web pages, navigate browser tabs, or interact with browser-visible applications without having administrator privileges. This can lead to unauthorized information disclosure and manipulation of browser sessions. The severity is high with a CVSS score of 8.3, indicating significant confidentiality and integrity impact, and a low availability impact. The practical impact depends on the browser profile and signed-in state of the user.
Mitigation Recommendations
Upgrade OpenClaw to version 2026.7.1 or later, where the administrator scope enforcement on browser control via node.invoke is correctly implemented. No other mitigation is required as the fix addresses the root cause.
OpenClaw (npm package 'openclaw') before 2026.7.1 does not enforce the administrator scope requirement on browser control when it is reached through… (CVE-2026-100588)
Description
OpenClaw (npm package 'openclaw') versions before 2026.7.1 have a security vulnerability where the administrator scope requirement is not enforced on browser control when accessed via the node.invoke method. This allows a write-scoped caller with access to a connected browser-capable node to perform actions such as inspecting pages, navigating tabs, or interacting with browser-visible applications without needing administrator privileges. The vulnerability is fixed in version 2026.7.1.
CVSS v3.1
Score 8.3high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The OpenClaw npm package prior to version 2026.7.1 does not enforce the administrator scope requirement on browser control when accessed through the node.invoke method, despite direct browser.request access requiring administrator scope. In Gateway deployments that respect caller identity and narrower operator scopes, this flaw allows a write-scoped caller to interact with browser-capable nodes beyond their intended privileges. Shared-secret token and password callers, considered fully trusted, are not affected. The issue is resolved in version 2026.7.1.
Potential Impact
An attacker or user with write-scoped access to a connected browser-capable node can inspect web pages, navigate browser tabs, or interact with browser-visible applications without having administrator privileges. This can lead to unauthorized information disclosure and manipulation of browser sessions. The severity is high with a CVSS score of 8.3, indicating significant confidentiality and integrity impact, and a low availability impact. The practical impact depends on the browser profile and signed-in state of the user.
Mitigation Recommendations
Upgrade OpenClaw to version 2026.7.1 or later, where the administrator scope enforcement on browser control via node.invoke is correctly implemented. No other mitigation is required as the fix addresses the root cause.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-234j-jv97-3432
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-100588"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6ab74f28f7a7c54106e1381e
Added to database: 09/26/2026, 04:50:48 UTC
Last enriched: 09/26/2026, 04:53:56 UTC
Last updated: 09/26/2026, 05:34:07 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.