Wwwvwwvwwwwwvwwvw

**Name of the Vulnerable Software and Affected Versions** OpenClaw versions 2026.2.26 through 2026.7.0 **Description** On Windows hosts running in exec allowlist mode, PowerShell command analysis may approve an executable resolved from PATH but execute a different file with the same name located in the workspace directory. This occurs when a command uses a bare executable name, allowing lower-trust content to place a malicious executable with an approved basename into an agent-writable workspace. Consequently, the agent may execute the workspace file instead of the intended allowlisted path, leading to arbitrary code execution with the privileges of the Gateway or node-host user. **Recommendations** Update to version 2026.7.1. Avoid using bare executable names in approved PowerShell commands. Keep executable files out of agent-writable workspaces.

**Name of the Vulnerable Software and Affected Versions** OpenClaw Codex versions prior to 2026.7.1 **Description** Insufficient owner authorization enforcement occurs during the creation of native conversation bindings. This allows non-owner channel senders who possess command access to establish bindings to the native Codex runtime. Consequently, these users can execute host-capable turns, granting them unauthorized access to files, tools, and processes. **Recommendations** Update OpenClaw Codex to version 2026.7.1 or later.

**Name of the Vulnerable Software and Affected Versions** OpenClaw versions prior to 2026.7.1 **Description** Insufficient validation of owner authorization occurs within the Codex computer-use installation command. This allows senders in a channel who are not owners to install arbitrary plugins and execute Model Context Protocol (MCP) processes—a standard for connecting AI models to external data sources—using the privileges of the OpenClaw user. This issue impacts the confidentiality, integrity, and availability of the host system. **Recommendations** Update to version 2026.7.1.

**Name of the Vulnerable Software and Affected Versions** OpenClaw versions prior to 2026.7.1 **Description** The software fails to enforce the administrator scope requirement for browser control when accessed via the `node.invoke` method, despite direct `browser.request` access requiring such scope. In Gateway deployments that utilize caller identity and narrow operator scopes, a caller with write-scope access to a browser-capable node can inspect pages, navigate tabs, or interact with browser-visible applications without administrator privileges. The actual impact depends on the browser profile and the current signed-in state. Callers using shared-secret tokens or passwords are not affected as they are treated as fully trusted operators. **Recommendations** Update to version 2026.7.1.

**Name of the Vulnerable Software and Affected Versions** OpenClaw versions prior to 2026.7.1 **Description** A sandbox bypass exists in the browser tool that allows sandboxed sessions to access paired node browser actions, even when the `allowHostControl` variable is set to `false`. An attacker who controls sandboxed agent input can select a paired node to perform host browser operations, enabling the inspection or manipulation of the connected browser profile and its authenticated state. **Recommendations** Update to version 2026.7.1 or later.

**Name of the Vulnerable Software and Affected Versions** OpenClaw versions 2026.5.1 through 2026.7.0 **Description** The software fails to apply the configured execution approval path to Google Meet node commands. Specifically, the `googlemeet.chrome` command accepts caller-supplied audio command arrays and executes them on a paired node, bypassing the standard `system.run` approval flow. In environments where the Google Meet plugin is enabled, a paired Chrome node exists, and the `googlemeet.chrome` command is permitted, an agent with tool-invocation capabilities can execute arbitrary processes on the paired node. This can lead to the compromise of files, credentials, and browser profiles, as well as impact system availability. **Recommendations** Update to version 2026.7.1. Remove `googlemeet.chrome` from the list of allowed node commands. Disable the Google Meet plugin.